A few common things: Check your clock.
Being everything (client, squid, target HTTP server) on localhost I don't think that clock might be an issue, anyway it's NTP synchronized and to the best of my knowledge it's pretty much correct. :-)
check your no_cache rules..
No no_cache rules apart from the stock one:
no_cache deny QUERY
What kinda bugs me is that the stock installation (./configure, make, make_install) plus the following configuration:
# diff -u squid.conf.default squid.conf --- squid.conf.default 2003-08-22 23:38:14.000000000 +0200 +++ squid.conf 2003-08-23 16:33:04.000000000 +0200 @@ -59,7 +59,7 @@ # internal address:port in http_port. This way Squid will only be # visible on the internal address. # Squid normally listens to port 3128 -http_port 3128 +http_port 3128 accel defaultsite=localhost:81
# TAG: https_port # Note: This option is only available if Squid is rebuilt with the @@ -555,6 +555,10 @@ # #Default: # none +cache_peer 127.0.0.1 parent 81 0 no-query originserver name=localhost +acl origin dstdomain localhost +cache_peer_access localhost allow origin +http_access allow origin
# TAG: cache_peer_domain # Use to limit the domains for which a neighbor cache will be
is behaving in a very weird way: all I see in the logs are TCP_CLIENT_REFRESH_MISS/200 if I try with manual telnet. If I use a browser sometimes I get TCP_CLIENT_REFRESH_MISS/304 (which is better, while still not enough) but still I can't manage to get a TCP_HIT anywhere, with or without ESI. Weird, weird, weird, and definitely different from 2.5 behaviour at a very least).
Ciao,
-- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Now blogging at: http://blogs.cocoondev.org/gianugo/)
