Re: [squid-users] Re: Squid 3.4 Head can't cache static url

On 23/04/2013 1:52 a.m., syaifuddin wrote:
> header and respond

NOTE: when dealing with a proxy there are *two* pairs of
request/response to check. One set client-squid and the other
squid-server. Both have an effect on the transaction cacheability.

As does the traffic mode.

>
> http://www.megalink-online.com/images/logo-d-link.jpg
>
> GET /images/logo-d-link.jpg HTTP/1.1

This is a port-80 format request. Are you intercepting?

> Host: www.megalink-online.com
> Connection: keep-alive
> Cache-Control: max-age=0

This is an instruction from the requestor *not* to use any cached
objects when responding. The response is always supposed to be a MISS.

> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.31 (KHTML, like
> Gecko) Chrome/26.0.1410.64 Safari/537.31
> Referer:
> http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-3-4-Head-can-t-cache-static-url-td4659576.html
> Accept-Encoding: gzip,deflate,sdch
> Accept-Language: en,id;q=0.8,en-US;q=0.6
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
> If-Modified-Since: Tue, 18 Oct 2011 04:23:16 GMT
>
> HTTP/1.1 304 Not Modified
> Server: nginx admin
> Date: Mon, 22 Apr 2013 13:49:56 GMT
> Last-Modified: Tue, 18 Oct 2011 04:23:16 GMT
> Connection: keep-alive
> Expires: Mon, 29 Apr 2013 13:49:56 GMT
> Cache-Control: max-age=604800
> X-Cache: HIT from Backend

This response says there was a cached object considered (HIT), and the
answer to the clients If-Modified-Since question is UNMODIFIED. It looks
perfectly correct and normal to me.

Your report was that Squid was not caching URLs, but this *is* caching
(somewhere). So....
   Where is the server named "Backend"?
     what caching software is it running?
     and how did the request get there? (what path through what
software, delivered by what means?)

Amos
Received on Tue Apr 23 2013 - 04:27:05 MDT