Daniel Vollbrecht wrote:
I configured Squid (3.0 STABLE7) in web accelerator mode to speed up a slow dynamic website. Now all img and css files are completely served by squid. They don't show up on the slow machine 10.1.1.2. But the dynamic content itself always (page reload, other clients) leds to a request to the slow machine: --- 8< --- 1225483916.728 444 10.1.1.254 TCP_REFRESH_MODIFIED/200 8889 GET http://www.mydomain.de/test.html - FIRST_UP_PARENT/10.1.1.2 text/html 1225483917.113 0 10.1.1.254 TCP_IMS_HIT/304 283 GET http://www.mydomain.de/img/pic.gif - NONE/- image/gif --- >8 --- Even with all the http-standard violating options for refresh_pattern that I used (config see below). The expected result should be that the slow machine only receives requests once within 30 min. Is something wrong in my config or what is your suggestion?
Are the dynamically generated pages given proper expiry information? (Expires: or Cache-Control: headers)
What the TCP_REFRESH_MODIFIED means is that a IMS request was sent to verify the data, but the server returned a full object with changes instead of a 304.
You are testing by using the force reload button on the browser right? Thats sending a must-revalidate request through to Squid which triggers an IMS.
Amos
-------- squid.conf ---------- http_port 10.1.1.1:80 accel defaultsite=www.mydomain.de vhost cache_peer 10.1.1.2 parent 80 0 no-query originserver cache_mgr cacheproblem@xxxxxxxxxxx # restrict access acl okdomains dstdomain www.mydomain.de mydomain.de http_access allow okdomains acl cache urlpath_regex \? never_direct allow cache refresh_pattern . 10 80% 30 override-expire override-lastmod ignore-reload ignore-no-cache ignore-no-store ignore-private url_rewrite_host_header off # cache tuning cache_mem 32 MB maximum_object_size_in_memory 40 KB maximum_object_size 32 MB cache_replacement_policy heap GDSF -------- squid.conf ---------- Thanks, Daniel
-- Please be using Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10 Current Beta Squid 3.1.0.1
