Re: [squid-users] Cache problem with SSL bridge

tis 2007-01-23 klockan 11:49 +0100 skrev p.lelievre@tiscali.fr:

> Here is an example of the headers in https mode :
>
> 1169479056.660 1485 192.168.7.1 TCP_MISS/200 1475123 GET
> https://ged.myoffice.fr/EDM/Documents/vmscsi-1.2.0.4.flp -
> FIRST_UP_PARENT/192.168.8.3 application/octet-stream [Accept:
> image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*\r\nReferer:
> https://ged.myoffice.fr/EDM/Documents/\r\nAccept-Language: fr\r
> \nAccept-Encoding: gzip, deflate\r\nUser-Agent: Mozilla/4.0
> (compatible; MSIE 6.0; Windows NT 5.0)\r\nHost: ged.myoffice.fr\r
> \nConnection: Keep-Alive\r\nCookie:
> ASPSESSIONIDCSBAAQBS=EEJPIDGCECCLGIODIPBJAJLI\r\nAuthorization: Basic
> QWRtaW5pc3RyYXRvcjpyb290\r\n] [HTTP/1.1 200 OK\r\nServer:
> Microsoft-IIS/5.0\r\nDate: Mon, 22 Jan 2007 15:17:35 GMT\r
> \nMicrosoftTahoeServer: 1.0\r\nCache-Control: public\r\nConnection:
> keep-alive\r\nContent-Type: application/octet-stream\r
> \nContent-Length: 1474560\r\nETag:
> "129fae11d5da094f989294fa5051a15a000000016a72"\r\nLast-Modified: Thu,
> 11 Jan 2007 10:44:04 GMT\r\nAccept-Ranges: bytes\r\nMS-WebStorage:
> 6.0.6511\r\nCache-Control: max-age=0\r\n\r]

There is authentication.. but response marked public so it's OK.

But the last Cache-Control: max-age=0 is not so good... max-age=0 tells
Squid that the content should be revalidated with the origin server on
each request, effectively not cachable. You can override this in
refresh_pattern, but I strongly advice configuring the server to return
better cache-control headers if you want the content cached as this also
applies to browser caches.

Regards
Henrik