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
