Re: [squid-users] HTTP Headers

On Monday 21 April 2003 19.33, Craig Kelley wrote:
> On Wed, 2003-03-05 at 15:50, Henrik Nordstrom wrote:
> > On Wednesday 05 March 2003 23.18, Craig Kelley wrote:
> > > 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 (?).

> When I attempt to set this up, I get no caching. From my store.log
> I see these entries:
>
> 1050944461.780 RELEASE -1 FFFFFFFF A517A3F93DAA31ADBE34FBD0D31BBFD3
> 200 1050944461 1050942166 -1 text/plain 25600/25600 GET
> http://ibncache/test2.dat
>
> Which, if I'm interpreting this correctly, means that it is
> successfully parsing the Last-Modified header, but the "Expires"
> (reply->expires) entry in the cache is set to "-1" for some reason.

Most likely Squid does not realize that the authentication is to Squid
and not the origin web server, and the rules of RFC2616 14.8
Authorization still triggers.. (Squid only supports rule #3,
Cache-Control: public).

See httpCachableReply().

Regards
Henrik

-- 
Donations welcome if you consider my Free Squid support helpful.
https://www.paypal.com/xclick/business=hno%40squid-cache.org
If you need commercial Squid support or cost effective Squid or
firewall appliances please refer to MARA Systems AB, Sweden
http://www.marasystems.com/, info@marasystems.com