Re: [squid-users] Squid does not obey must-revalidate / proxy-revalidate ?

Hi Warrick,

It seems to work fine here. I removed the Content-Location and
Last-Modified header appends you have in your example, but I don't think
that is relevant. Everything else about my test case is the same as
your listed options.

Try enabling mime_hdrs in the access.log to see what is happening with
the request. I'm seeing a response from the origin every time I hit the
page (Not Modified...but it forces authentication when I log in from
another client machine or another browser (that doesn't have auth info
cached).

I may be misreading my logs, but it /does/ appear that the first GET
(the one that requires authentication) always MISSes. This might be
necessary for authentication to work. Subsequent loads of the page on
the other client, however, are always HITs. Sounds about like what you
want.

Warrick FitzGerald wrote:
> Hi All,
>
> I'm not sure if I'm missing something here, but some reason I can not
> for the life of me get squid to re-validate a page that it has recieved
> with a proxy-revalidate header.
>
> In apache I have an .htaccess file that looks like this.
> -------------------------------------------------------------
> AuthType Basic
> AuthName "By Invitation Only"
> AuthUserFile /tmp/htpass
> Require user warrick
>
> Header append Cache-control public,proxy-revalidate
> Header append Content-Location: "http://my.test.proxy/"
> Header append Last-Modified "Fri, 17 May 2002 23:56:14 GMT"
>
> -------------------------------------------------------------
>
> Squid lakes in the page just fine and caches is. However when the client
> sends the IMS request ... squid does not relay this back to the origin
> server ?
>
>
> Any ideas ?
>
>
> Thanks
> Warrick FitzGerald
> Senior Systems Engineer
> LiveTechnology Inc.
> Office. 914 251 9230 ext 102
> Cell. 914 755 6161
>

-- 
Joe Cooper <joe@swelltech.com>
Web caching appliances and support.
http://www.swelltech.com