NIGHTMARE cache issue reverse proxy. Objects in cache replaced with 0 bytes and not being fetched from upstream

[David Taveras]

In regards to the 304 "if none matched" bug fixed in 0.7.65 could
anybody tell me if this bug is also available in the legacy stable
version 0.6.39 ??

Thanks.

David

On Tue, Apr 13, 2010 at 8:23 AM, David Taveras <d3taveras38d3 at gmail.com> wrote:
> Correct, iam using 0.7.64 .. it seems this bug was fixed in 0.7.65 ...
>
> Thank you.
>
> David
>
> On Tue, Apr 13, 2010 at 6:52 AM, Ryan Malayter <malayter at gmail.com> wrote:
>> On Tue, Apr 13, 2010 at 3:21 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:
>>
>>>> What could be causing this mess???
>>>
>>> http://tools.ietf.org/html/rfc2616#section-10.3.5
>>
>> I think David is referring to the 304 response being cached by nginx,
>> which of course it should not:
>>
>> >From the RFC:
>>   If a cache uses a received 304 response to update a cache entry, the
>>   cache MUST update the entry to reflect any new field values given in
>>   the response.
>>
>> Isn't this a symptom the "If-None-Match" bug that was recently fixed?
>> I ran into the same thing myself a while back using 0.7.62.
>>
>> --
>> RPM
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://nginx.org/mailman/listinfo/nginx
>>
>