fre 2007-02-02 klockan 12:52 +0100 skrev p.lelievre@xxxxxxxxxx: > I'm not sure to well understand the problem : for me, max-age=0 just tells squid to revalidate data at each request but not to reload it if cached data is still good. > Above all, without SSL, in HTTP mode, I have the same headers with max-age=0, but with an ethernet sniffer I can see squid revalidating data but not reloading it. That seems good for me. > Don't you think it could be a bug in squid but only in https mode ? Works for me when I try to replicate your setup using the headers from your log. First request gets forwarded without If-Modified-Since, second request has a If-Modified-Since. GET /a HTTP/1.0 If-Modified-Since: Thu, 11 Jan 2007 10:44:04 GMT Via: 1.0 henrik:3128 (squid/2.6.STABLE8-CVS) X-Forwarded-For: 127.0.0.1 Host: test.ssl Cache-Control: max-age=259200 Connection: keep-alive https_port 127.0.0.1:4443 cert=/home/henrik/squid/etc/cert1.pem key=/home/henrik/squid/etc/cert1_key.pem accel defaultsite=test.ssl cache_peer 127.0.0.1 parent 4433 0 no-query originserver name=ssl no-digest no-netdb-exchange ssl sslcafile=/home/henrik/squid/etc/test.pem Technically there should be a If-None-Match as well as the object has an ETag, but that's missing for some reason. Probably not implemented for non-Vary:ing objects.. Regards Henrik
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel
