RE: [squid-users] Cache authenticated data

> Amos thank you for the help.
>
> I set the following:
> authenticate_ttl 0 seconds
> authenticate_ip_ttl 3 seconds
>
> Delete SQUID cache folder and run squid -z
>
> The first request needs to be authenticate.
> The second request was from a different computer with a different IP 15
> minutes after the first request and no authentication was required.
>
> Any thoughts?

Really weird.

What are the exact headers the serevr is giving squid?

Amos

>
> -----Original Message-----
> From: Amos Jeffries [mailto:squid3@treenet.co.nz]
> Sent: Thursday, January 24, 2008 10:47 AM
> To: Tomer Brand
> Cc: squid-users@squid-cache.org
> Subject: Re: [squid-users] Cache authenticated data
>
> Tomer Brand wrote:
>> Hi,
>>
>> I am trying to use SQUID to cache IIS data.
>> The IIS is configured to use basic authentication. I set the response
> header with:
>> Cache Control -> public, must-revalidate
>> And then changed it to:
>> Cache Control -> public, no-cache
>>
>> My SQUID cache_peer is:
>> cache_peer images.test.com parent 8050 0 originserver default
> login=PASS
>>
>> I run into two issues:
>> 1. Only the first request is asked to authenticate, the second one
> simply get the data.
>> 2. I don't see any new data in the cache directory.
>>
>> What am I missing?
>
> no-cache == no don't save AKA new data in cache dir.
> must-revalidate == always check for new, even if old gets sent.
>
> Check your authenticate_ttl and authenticate_ip_ttl values are short
> enough for your testing.
>
>
> Amos
> --
> Please use Squid 2.6STABLE17+ or 3.0STABLE1+
> There are serious security advisories out on all earlier releases.
>
Received on Thu Jan 24 2008 - 13:56:26 MST