Re: [squid-users] Whis this dosn't cache??

On 4/07/2013 10:13 a.m., Eliezer Croitoru wrote:
> Amos this is one of the weirdest things I have ever seen!!
> the more in depth logs shows a 304 request and response while the
> access log shows 200.

The cache.log snippets you display below show 200 with the server.
access.log should be showing the status delivered to the client. Where
is the 304 you speak of?

I woudl expect to see a request from client, a IMS/304 with server and a
200 or 304 resulting to the client.

> So I noticed that there is a Pragma header present like this:
> ##start
> 2013/07/04 01:10:16.067 kid1| http.cc(2199) sendRequest: HTTP Server
> REQUEST:
> ---------
> GET
> /rhintrotoglusterfsoct11final-111028123627-phpapp01/95/slide-21-728.jpg?1319823419
> HTTP/1.1
> Host: image.slidesharecdn.com
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101
> Firefox/22.0
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language: en-US,en;q=0.5
> Accept-Encoding: gzip, deflate
> Pragma: no-cache
> Cache-Control: no-cache
> Connection: keep-alive

Pragma should no longer be havig any effect at all for Squid unless
Cache-Control header is completely absent.

>
> ----------
> 2013/07/04 01:10:16.102 kid1| ctx: enter level 0:
> 'http://slidesharecdn.squid.internal/rhintrotoglusterfsoct11final-111028123627-phpapp01/95/slide-21-728.jpg'
> 2013/07/04 01:10:16.102 kid1| http.cc(749) processReplyHeader: HTTP
> Server local=192.168.10.1:43176 remote=88.221.156.163:80 FD 13 flags=1
> 2013/07/04 01:10:16.102 kid1| http.cc(750) processReplyHeader: HTTP
> Server REPLY:
> ---------
> HTTP/1.1 200 OK
> x-amz-id-2:
> boib9MhPcFDoBTAhOtCPIhnJMcp663cUNfLv6JWFcrwRnFdYATNFjpF74A35ZYrq
> x-amz-request-id: A2AB3473F4965692
> Last-Modified: Tue, 22 May 2012 21:39:08 GMT
> x-amz-version-id: c1_r1OArnftwzoomQNKDfuXd75JYVaEn
> ETag: "b93088a8bb9fdaa382f0755077343b21"
> Accept-Ranges: bytes
> Content-Type: image/jpeg
> Server: AmazonS3
> Vary: Accept-Encoding
> Content-Encoding: gzip
> Content-Length: 98354
> Cache-Control: max-age=31536000
> Date: Wed, 03 Jul 2013 22:10:36 GMT
> Connection: keep-alive

Server is a bit broken. Sending us "new" content which is well past its
max-age value already.

>
> �
> ##END
>
> So actually what can cause this kind of a problem??
> the 304 is what I would have expected but I see that Pragma effect
> some requests.
> Can we disable Pragma Headers without modifying the request using ICAP?

Only by removing the Pragma header completely. But 3.3+ should not be
using Pragma unless Cache-Control is completely absent.

Amos
Received on Thu Jul 04 2013 - 01:20:25 MDT