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@gmail.com> wrote:
> On Tue, Apr 13, 2010 at 3:21 AM, Maxim Dounin <mdounin@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@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx