Re: Cache revalidate modified timezone mismatch

2014-05-07 Thread Thijs Koerselman
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 wrote: > On 7 May 2014 15:51, Thijs Koerselman wrote: > > I have a backend returning a last modified header in CEST. > > RF2616 says "

Re: Cache revalidate modified timezone mismatch

2014-05-07 Thread Jonathan Matthews
On 7 May 2014 15:51, Thijs Koerselman 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. > Wh

Re: Cache revalidate modified timezone mismatch

2014-05-07 Thread Thijs Koerselman
I'm using version 1.5.12 btw. On Wed, May 7, 2014 at 4:51 PM, Thijs Koerselman wrote: > I have a backend returning a last modified header in CEST. > > I'm using a 1sec proxy that revalidates as described here: > http://whitequark.org/blog/2014/04/05/page-caching-with-nginx/ > > My problem is tha

Cache revalidate modified timezone mismatch

2014-05-07 Thread Thijs Koerselman
I have a backend returning a last modified header in CEST. I'm using a 1sec proxy that revalidates as described here: http://whitequark.org/blog/2014/04/05/page-caching-with-nginx/ My problem is that when nginx makes the request to the backend it changes CEST into GMT, without adjusting the time.