Re: [squid-users] Non-cached pages with squid 2.5-stable13
Mark Elsen wrote: Hi Mark, thank you for that tool. It reports: http://[...]/cache/setHeader.php/getTheList Expires 35 sec from now (Sun, 19 Mar 2006 10:49:01 GMT) Cache-Control - Last-Modified 25 sec ago (Sun, 19 Mar 2006 10:48:01 GMT) validation returned same object ETag - Content-Length 6.3K (6438) Server Apache This object will be fresh for 35 sec. It has a validator present, but when a conditional request was made with it, the same object was sent anyway. I've read that squid might not be caching it, since the expires is less than 60 seconds in the future. Is that true? But even rasing the limit returned (currently 60 seoncds, maybe raising it to 120) does not work for me. What does the validation returned same object mean and why is it printed in read? Not sure, what is returned for this object with : http://web-sniffer.net ? Hmm - does not show anything special either. But during tries to track this down it showed that most of the time I received TCP_MEM_HIT, but sometimes a row of TCP_REFRESH_MISS occured for a duration of 10 or 20 seconds (1 request per sec) out of no obvious reason and only sporadic. It seems this occured with and without the collapsed forwarding-patch. I'll try to find a good way to reliable diagnose it before continuing this thread. Thank you for your help so far. Regards, Stefan
Re: [squid-users] Non-cached pages with squid 2.5-stable13
Mark Elsen wrote: On 3/19/06, Stefan Neufeind [EMAIL PROTECTED] wrote: Hi, at the moment I did try to run a squid 2.5-stable13 from Fedora Core 4, handpatched with collapsed-forwarding-support and epoll. Those two additional features work quite well. But currently I experience some pages which unfortunately are not cached by squid. ... ... http://www.ircache.net/cgi-bin/cacheability.py Hi Mark, thank you for that tool. It reports: http://[...]/cache/setHeader.php/getTheList Expires 35 sec from now (Sun, 19 Mar 2006 10:49:01 GMT) Cache-Control - Last-Modified 25 sec ago (Sun, 19 Mar 2006 10:48:01 GMT) validation returned same object ETag - Content-Length 6.3K (6438) Server Apache This object will be fresh for 35 sec. It has a validator present, but when a conditional request was made with it, the same object was sent anyway. I've read that squid might not be caching it, since the expires is less than 60 seconds in the future. Is that true? But even rasing the limit returned (currently 60 seoncds, maybe raising it to 120) does not work for me. What does the validation returned same object mean and why is it printed in read? Regards, Stefan
Re: [squid-users] Non-cached pages with squid 2.5-stable13
Hi Mark, thank you for that tool. It reports: http://[...]/cache/setHeader.php/getTheList Expires 35 sec from now (Sun, 19 Mar 2006 10:49:01 GMT) Cache-Control - Last-Modified 25 sec ago (Sun, 19 Mar 2006 10:48:01 GMT) validation returned same object ETag - Content-Length 6.3K (6438) Server Apache This object will be fresh for 35 sec. It has a validator present, but when a conditional request was made with it, the same object was sent anyway. I've read that squid might not be caching it, since the expires is less than 60 seconds in the future. Is that true? But even rasing the limit returned (currently 60 seoncds, maybe raising it to 120) does not work for me. What does the validation returned same object mean and why is it printed in read? Not sure, what is returned for this object with : http://web-sniffer.net ? M.
Re: [squid-users] Non-cached pages with squid 2.5-stable13
sön 2006-03-19 klockan 11:53 +0100 skrev Stefan Neufeind: I've read that squid might not be caching it, since the expires is less than 60 seconds in the future. Is that true? The 60 seconds limit is only on objects not having an cache validator (i.e. Last-Modified). What does the validation returned same object mean and why is it printed in read? The cacheability check engine when finding a cache validator sens a conditional request with this validator (i.e. If-Modified-Since condition for the Last-Modified validator). Your server responded to this with a full identical response rather than the 304 Not modified that was expected. This is undesired, but not related to your problem. Regards Henrik signature.asc Description: Detta är en digitalt signerad meddelandedel
[squid-users] Non-cached pages with squid 2.5-stable13
Hi, at the moment I did try to run a squid 2.5-stable13 from Fedora Core 4, handpatched with collapsed-forwarding-support and epoll. Those two additional features work quite well. But currently I experience some pages which unfortunately are not cached by squid. I wonder why - and wonder if it might have to do with vary-headers the webserver is sending. A called script returns: Date: ... (current date) Server: Aapche Expires: ... (like date, approx 2min in the future) Last-Modified: ... (shortly before Date) Vary: Accept-Encoding Content-Length: ... Connection: close Content-Type: text/html The Vary-header is used to deliver gzip-compressed or non-compressed content (compressed inside php) to the clients which do/don't support it. Though I _think_ everything should be fine upon each request to squid for this object squid includes an If-Modified-Since in it's request which is already more than 2 hours in the past - might be the time when squid was started and/or first tried to cache a copy of the page. Both the squid and the webserver are in sync. Is there a possibility why squid does not cache the content, and why it might be using an IMS that far back in the past? Static content is cached fine - but that does not include Vary-headers or Expires. I've seen notes from (afaik) squid 2.5-stable11 that pages with vary-headers are now cached. Could this be related that in some special cases they are not yet? By the way: The squid is running in httpd_accel mode with proxy, in front of several webservers (which are in sync) defined via cache_peer. Any hints to track this down would be welcome! Yours sincerely, Stefan Neufeind
Re: [squid-users] Non-cached pages with squid 2.5-stable13
On 3/19/06, Stefan Neufeind [EMAIL PROTECTED] wrote: Hi, at the moment I did try to run a squid 2.5-stable13 from Fedora Core 4, handpatched with collapsed-forwarding-support and epoll. Those two additional features work quite well. But currently I experience some pages which unfortunately are not cached by squid. ... ... http://www.ircache.net/cgi-bin/cacheability.py M.
