Thanks Chris for the suggestions. I set negative_ttl to a large value. Seems like its not caching the 404 responses.... 1210106683.175 63 192.168.75.133 TCP_MISS/404 1525 GET http://www.google.com/idontexist - DIRECT/209.85.173.147 text/html 1210106684.945 41 192.168.75.133 TCP_MISS/404 2943 GET http://www.google.com/idontexist - DIRECT/209.85.173.147 text/html works find on 200 responses... 1210107245.606 56 192.168.75.133 TCP_MISS/200 6619 GET http://www.google.com/ - DIRECT/209.85.173.147 text/html 1210107246.572 0 192.168.75.133 TCP_MEM_HIT/200 6496 GET http://www.google.com/ - NONE/- text/html Any ideas? Christian ----- Original Message ---- From: Chris Robertson <crobertson@xxxxxxx> To: squid-users@xxxxxxxxxxxxxxx Sent: Tuesday, May 6, 2008 1:25:25 PM Subject: Re: cache of 404 and redirects Christian Seifert wrote: > Hi there, is there a way to instruct squid to cache pages that return errors and redirects, like 404 and 302? > As for the 404s look to the "negative_ttl" directive (http://www.squid-cache.org/Versions/v2/2.6/cfgman/negative_ttl.html). 302s need to be sent with expiry information to be cacheable. See http://www.squid-cache.org/mail-archive/squid-users/200701/0001.html for more info. > Thx > Christian Chris ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
