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

2009-07-01 Thread Jason Noble
but it feels like you are trying to accomplish something very unusual/weird Perhaps some more background information is in order here. What we are trying to accomplish is acceleration on a Zope/Plone CMS. The CacheFu product is primarily responsible for setting cache headers and issuing

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

2009-07-01 Thread Jason Noble
As mentioned in my previous e-mail, we are working to implement caching of anonymous/authenticated versions of pages in a Zope/Plone environment. In a discussion in 2005 revolving around this same subject, you recommended to a user that they use ETags instead of Vary: Cookie in this

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

2009-07-01 Thread Henrik Nordstrom
ons 2009-07-01 klockan 16:45 -0400 skrev Jason Noble: As mentioned in my previous e-mail, we are working to implement caching of anonymous/authenticated versions of pages in a Zope/Plone environment. Ah.. As you probably know by now HTTP cache model isn't really designed for that.. content

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

2009-06-29 Thread Henrik Nordstrom
fre 2009-06-12 klockan 13:02 -0400 skrev Jason Noble: 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.

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

2009-06-26 Thread Alex Rousskov
On 06/16/2009 08:13 AM, Jason Noble wrote: You're right, looks like I read that section too quickly. After reading the RFC more carefully, it appears that the case I'm having issues with is undefined. The closest thing I can find is 13.3.4: An HTTP/1.1 caching proxy, upon receiving a

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

2009-06-16 Thread Jason Noble
You're right, looks like I read that section too quickly. After reading the RFC more carefully, it appears that the case I'm having issues with is undefined. The closest thing I can find is 13.3.4: An HTTP/1.1 caching proxy, upon receiving a conditional request that includes both a

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

2009-06-15 Thread Jason Noble
From RFC 2616 13.6: ... When the cache receives a subsequent request whose Request-URI specifies one or more cache entries including a Vary header field, the cache MUST NOT use such a cache entry to construct a response to the new request unless all of the selecting request-headers present in

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

2009-06-15 Thread Mark Nottingham
Selecting request headers are specified by Vary; If-None-Match is a conditional request header. Cheers, On 16/06/2009, at 12:44 AM, Jason Noble wrote: From RFC 2616 13.6: ... When the cache receives a subsequent request whose Request-URI specifies one or more cache entries including a

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

2009-06-12 Thread Mark Nottingham
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