Sorry, I've forgotten the details again: Squid Cache: Version 2.7.STABLE9-20101104 configure options: '--prefix=/squid2' '--enable-async-io' '--enable-icmp' '--enable-useragent-log' '--enable-snmp' '--enable-cache-digests' '--enable-follow-x-forwarded-for' '--enable-storeio=null,aufs' '--enable-removal-policies=heap,lru' '--with-maxfd=16384' '--enable-poll' '--disable-ident-lookups' '--enable-truncate' '--with-pthreads' 'CFLAGS=-DNUMS=60 -march=nocona -O3 -pipe -fomit-frame-pointer -funroll-loops -ffast-math -fno-exceptions' '--enable-htcp' On Tue, Nov 16, 2010 at 10:58 AM, david robertson <dr@xxxxxxxxxxxx> wrote: > Hello, I have a bit of an urgent issue - Squid is serving 400 errors, > and I'd like to avoid that. Ideally, we want Squid to serve the > object that it has in cache, instead of the 400. I have > stale-if-error=1800 in the headers, but squid is still serving a 400 > whenever it gets it from the origin (webserver). We don't want 400's > served at all. > > So, as the subject says, does a stale-if-error header apply to 400 > status requests? >
