Amos Jeffries wrote > 1) broken cacheability headers. > The Expires: header says (Date: + 360 days), and s-maxage says 360days > BUT ... Last-Modified says 1970. So Last-Modified + s-maxage is already > expired. > NP: this is not breaking Squid which still (incorrectly) uses Expires > header in preference to s-maxage. But when we fix that bug this server > will start to MISS constantly. So this is caused by the application? It is made by IBM, if you fix this bug, i guess we need to keep using the older version of Squid. Amos Jeffries wrote > Does the matching "HTTP Server REQUEST" to the parent peer for the > eclipse transaction contain an If-Modified-Since and/or If-Match header? Sorry, i didn't get that, would you please explain me in more detail? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Sibling-cache-peer-for-a-HTTPS-reverse-proxy-tp4667011p4667086.html Sent from the Squid - Users mailing list archive at Nabble.com.
