Thanks for the reply Henrik; this is strange though:
1) If I disable all authentication, everything works flawlessly. I can
retrieve a file and then subsequent requests hit the cache. If `touch`
it on the remote machine, then it re-fetches the file, just as it
should.
2) If I turn on basic HTTP authentication in Apache with something like
this, however:
AuthType Basic
AuthName ByPassword
AuthUserFile /var/www/secure/users
<Limit GET PUT POST DELETE>
Require valid-user
</Limit>
Then squid will always re-fetch the file regardless; a cache miss every
time. Is this an Apache problem? I would rather just have squid do the
basic authentication, but from what I understand it cannot reliably do
this when in httpd_accel mode (?).
On Tue, 2003-03-04 at 16:32, Henrik Nordstrom wrote:
> If your server send Last-Modified headers then Squid will use this and
> issues a If-Modified-Since request to validate the freshness of the
> cached copy when refresh_pattern says the file is stale..
>
> While refresh_pattern says that the file is fresh it is given directly
> from the cache without validating the freshness with the backend
> server.
>
> Regards
> Henrik
>
> On Tuesday 04 March 2003 20.39, Craig Kelley wrote:
> > Hello everyone;
> >
> > We have squid running in a transparent mode (httpd_accel) to
> > another server so that we can reduce the load over an expensive
> > link. Everything works great, but it seems that squid is not
> > checking the `last modified' http headers from the source server
> > (?) Is there a way to have squid check the http header from the
> > remote machine to determine whether or not a file needs to be
> > re-fetched, or does it simply go `stale' in the squid cache and
> > require re-fetching the whole file again?
> >
> > We're currently using these directives:
> >
> > httpd_accel_host 63.227.133.121
> > httpd_accel_port 80
> > httpd_accel_single_host on
> > httpd_accel_with_proxy off
> > httpd_accel_uses_host_header on
> >
> > Thanks,
> >
> > Craig Kelley
>
