Search squid archive

Responses to squidclient and browser are different

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I config the squid cache such that it caches pretty much everything and
pretends those pages are fresh for a long time. Specifically, I have this in
my squid.conf

acl my_machine src <ip>
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1

http_access allow my_machine
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports

refresh_pattern ^http: 600000 100% 700000 override-expire override-lastmod
reload-into-ims ignore-reload ignore-no-cache ignore-private ignore-no-store
ignore-must-revalidate ignore-auth

I also leave everything else the same in squid.conf as the default.

I tested the cache using squidclient, and it seems to work as expected. I
got HIT every time for http://techcrunch.com. I looked at the content, and
they were always the same. Then, I set my browser to direct http traffic to
localhost port 3128. It seemed to go thought squid cache, because when I
tried to load non-existing page, the error message I got was from squid
cache.

However, when I tried to load http://techcrunch.com, I did not get the same
stale page that I got when using squidclient. The browser always gave me a
real fresh page.

Why is it doing that? How can I make the browser respond with content in the
cache? Please help!




--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Responses-to-squidclient-and-browser-are-different-tp4663714.html
Sent from the Squid - Users mailing list archive at Nabble.com.




[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux