[squid-users] HIT on HEAD but MISS on GET?

I've noticed that Squid is having trouble caching an object which has
a Set-Cookie header. Here are the object's headers:

Date: Thu, 25 May 2006 15:34:09 GMT
Server: Apache/2.0.54 (Debian GNU/Linux) mod_ssl/2.0.54 OpenSSL/0.9.7e
mod_apreq2-20051231/2.5.7 mod_perl/2.0.2 Perl/v5.8.4
Set-Cookie: NNNSSID=f441217251ca7cc1aa62506590894578; expires=Thu, 25
May 2006 16:34:09 GMT; path=/
Last-Modified: Wed, 24 May 2006 20:49:12 GMT
ETag: "9bd16b-7c80cf-de294200"
Accept-Ranges: bytes
Content-Length: 8159439
Content-Type: text/plain; charset=UTF-8

When I send HEAD requests (using curl), the Squid cache behaves as I
would expect. The first request is a MISS and the headers include the
Set-Cookie line; subsequent requests are HITs and the headers do not
include Set-Cookie.

However, when I do the same thing with GET, the requests always return
MISS and include the Set-Cookie header. Sending a GET request also
makes the next HEAD request return a MISS.

Hopefully this is just a misconfiguration on my end; I swear this used
to work correctly... Any help is appreciated. Thanks in advance.

Lawrence
Received on Thu May 25 2006 - 09:35:51 MDT