On 21/06/2013 3:28 a.m., Paul Browne wrote:
Hi,
We are now running Squid 3.2.7 and find that our icap respmod responses are not
caching,
icap_service mib_request_xx reqmod_precache 0 icap://127.0.0.1:1344/xx/reqmod
icap_service mib_response_xx respmod_precache 0 icap://127.0.0.1:1344/xx/respmod
icap version 1.0f
Request:
curl -vvv --proxy 127.0.0.1:3128 http://<myicapapplication>/css/common.css
< Content-Type: text/css
< Cache-Control: max-age=14400
< Expires: Thu, 20 Jun 2013 11:45:26 PDT
< Last-Modified: Tue, 18 Jun 2013 09:58:15 GMT
< ETag: W/"56549-1371549495000"
< Content-Length: 65790
< Server: Apache-Coyote/1.1
< Date: Thu, 20 Jun 2013 14:45:26 GMT
< Vary: Accept-Encoding
< X-Cache: MISS from myserver.com
< X-Cache-Lookup: MISS from myserver:3128
< Via: internet
< Connection: keep-alive
Headers returned printed from app:
content-type: text/css
cache-control: max-age=14400
expires: Thu, 20 Jun 2013 11:45:26 PDT
last-modified: Tue, 18 Jun 2013 09:58:15 GMT
etag: W/"56549-1371549495000"
content-length: 65790
server: Apache-Coyote/1.1
date: Thu, 20 Jun 2013 14:45:26 GMT
vary: Accept-Encoding
Connection: keep-alive
ISTag: "RespModService"
When we don't request the css file through our icap application squid caches
fine,
PDT is an invalid timezone. HTTP requires GMT and that invalid dates are
treated as equivalent to "Expires: -1".
Making this a non-cacheable response.
Amos
