Re: [squid-users] delivering stale content while fetching fresh

On 2006/09/05, at 2:33 PM, Henrik Nordstrom wrote:

> The drawback of enabling collapsed_forwarding is that concurrent
> requests for uncachable content will get delayed a bit until Squid
> sees
> that the response can not be cached (response headers required), at
> which point all pending collapsed queries for that URL will all
> start a
> new request each..

I'm guessing that's the full URL. It would be nice if there were an
option to ignore the query string for this purpose;

E.g., if Squid sees
   http://example.com/search?q=foo
and finds it's uncacheable, it would then stop collapsing other
requests with the same base, e.g.,
   http://example.com/search?q=bar

Even better, a response cache-control extension could control this...

Cheers,

--
Mark Nottingham
mnot@yahoo-inc.com