On 09/12/10 21:28, Rodolfo Alcazar Portillo wrote:
On Wed, 2010-12-08 at 18:19 +1300, Amos Jeffries wrote:
On 08/12/10 16:51, Rodolfo Alcazar Portillo wrote:
With Firefox, "TCP_MEM_HIT":
1291778947.206 0 127.0.0.1 TCP_MEM_HIT/200 626 GET http://www.elpais.com/css/i_portadillas.css? - NONE/- text/css
...
The VERY SAME PAGE with Google Chrome, several reloads, always "TCP_MISS":
1291778941.929 108 127.0.0.1 TCP_MISS/304 340 GET http://www.elpais.com/css/i_portadillas.css? - DIRECT/80.157.169.17 text/css
...
You need to look at the headers they are sending Squid. See what is
different between the two.
The message turns to TCP_REFRESH_UNMODIFIED/304 after clearing chrome's
cache, but it still grabbing the css, jpg, etc. from the server for each
request.
Answering to your questions: Squid 3.1.9, I'm john doe browsing an
unknown server. Don't want to cache all by ignore-cc. Just want to cache
things like css or jpg.
Please check the chrome headers (I deleted the irrelevant, time of this
shot: 09:13):
Its clear from your message that something other than the usual timing
headers are affecting things.
Sadly the other headers I was going to check are not there, can you
supply the full headers please? use a.b.c.d or example.invalid to
obscure any IPs or domains you don't want to publish.
BROWSER REQUEST:
================
GET http://www.elpais.com/css/i_portadillas.css?update=13201012042222 HTTP/1.1
Cache-Control: max-age=0
If-Modified-Since: Sat, 04 Dec 2010 21:22:54 GMT
...
SQUID RESPONSE:
===============
HTTP/1.0 304 Not Modified
Last-Modified: Sat, 04 Dec 2010 21:22:54 GMT
Cache-Control: max-age=32222
Date: Thu, 09 Dec 2010 08:12:52 GMT
Warning: 110 squid/3.1.9 "Response is stale"
Warning: 111 squid/3.1.9 "Revalidation failed"
X-Cache: HIT from rodolfoap.rap.es
X-Cache-Lookup: HIT from rodolfoap.rap.es:3128
...
Squid log for this request:
1291882372.347 125 127.0.0.1 TCP_REFRESH_UNMODIFIED/304 432 GET http://www.elpais.com/css/i_portadillas.css? - DIRECT/80.156.250.8 text/css
(the same produces a HIT with firefox! chrome grabs the css every time). What are those warnings?
warning 110 indicates the object is known to be past its expiry time.
warning 111 indicates that squid did try to check for a newer version
but the server check failed.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.9
Beta testers wanted for 3.2.0.3
