Re: Problem with cached entries w/ETag and request without If-None-Match header

What requirement in RFC2616 does this violate?

On 13/06/2009, at 3:02 AM, Jason Noble wrote:

> I recently ran into a bug on Squid 2.7 regarding cached content with
> ETags. Currently, if all cached entries for a URL include ETags,
> and a request is received for said URL with no If-None-Match header,
> Squid will serve a cached entry. This behavior does not follow RFC
> 2616. I have attached a patch that prevents Squid from serving the
> cached entries in said case here: http://www.squid-cache.org/bugs/show_bug.cgi?id=2677
>
> I would appreciate any feedback regarding this patch.
>
> Thanks,
> Jason

--
Mark Nottingham       mnot_at_yahoo-inc.com