Client Cache-Control doesn't work?

Hi,

I'm investigating why my http client can't seem to disable caching for an
object. I send this request:

GET http://debian.midco.net/debian/dists/hamm/non-free/binary-i386/Release
HTTP/1.1
Host: debian.midco.net
Cache-Control: no-cache
If-Modified-Since: Fri, 24 Jul 1998 06:43:14 GMT
User-Agent: Debian APT-HTTP/1.2

and squid happily returns the object without querying the origin server,
which if I read rfc2068 correctly is wrong. I have also tried max-age=0
with no luck, as well as removing the IMS header.

Does squid not support HTTP/1.1 compliant cache-control?

I'm using squid 2.0.2

Also, why does squid insist on logging stuff like:
1998/12/06 01:27:00| clientKeepaliveNextRequest: FD 8 Sending next
1998/12/06 01:27:00| clientSendMoreData: Deferring
http://debian.midco.net/debian/dists/hamm/non-free/binary-i386/Release

When the client pipelines?

Thanks,
Jason
Received on Sun Dec 06 1998 - 03:24:51 MST