Cache revalidate modified timezone mismatch

Thijs Koerselman thijskoerselman at gmail.com
Wed May 7 20:13:32 UTC 2014


Aha good to know! I'm not responsible for this backend, so I'll harass my
colleague about it :) Thanks.

Thijs


On Wed, May 7, 2014 at 5:34 PM, Jonathan Matthews
<contact at jpluscplusm.com>wrote:

> On 7 May 2014 15:51, Thijs Koerselman <thijskoerselman at gmail.com> wrote:
> > I have a backend returning a last modified header in CEST.
>
> RF2616 says "All HTTP date/time stamps MUST be represented in
> Greenwich Mean Time (GMT), without exception".
>
> I'm not very surprised nginx isn't doing what you expect. Fix your backend.
>
> > What's going on
>
> I suspect nginx is merely munging the header into something that
> matches the HTTP spec, and (arguably correctly) isn't looking at the
> actual meaning of the header being modified.
>
> > and how can I fix this?
>
> Fix your backend.
>
> J
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140507/4f9ab1ec/attachment-0001.html>


More information about the nginx mailing list