Maxim Dounin Wrote:
---
> Nice catch. It's not a bug in nginx though, as HTTP only allows
> fixed-width subset of RFC1123, see here:
>
> http://tools.ietf.org/html/rfc2616#section-3.3.1
>
Thanks Maxim! Easy fix. Bug and patch submitted to Mon
Hello!
On Sun, Mar 03, 2013 at 08:02:45AM -0500, Daniel15 wrote:
> Maxim Dounin Wrote:
> ---
> > In ths particular case I would suggest there is another caching
> > layer, which results in cached "X-Cache: MISS" being returned.
> > Note that
Hello!
On Sun, Mar 03, 2013 at 07:45:21AM -0500, Daniel15 wrote:
> Figured it out.
>
> The Expires header ("Sun, 3 Mar 2013 13:28:24 GMT") is using a single digit
> for the date. If I change the "3" to "03", Nginx works as expected. RFC
> 1123 and RFC 822 say that both one- and two-digit numbe
Maxim Dounin Wrote:
---
> In ths particular case I would suggest there is another caching
> layer, which results in cached "X-Cache: MISS" being returned.
> Note that Expires and Last-Modified are the same, and
> X-ExecutionTime headers match
Hello!
On Sun, Mar 03, 2013 at 07:32:05AM -0500, Daniel15 wrote:
> Nginx's FastCGI caching used to work perfectly for me, but recently it
> stopped working and I can't work out why.
>
> This is how the headers look:
> HTTP/1.1 200 OK
> Server: nginx/1.2.7
> Date: Sun, 03 Mar 2013 12:28:24 GMT
>
Figured it out.
The Expires header ("Sun, 3 Mar 2013 13:28:24 GMT") is using a single digit
for the date. If I change the "3" to "03", Nginx works as expected. RFC
1123 and RFC 822 say that both one- and two-digit numbers are valid, so this
is a bug in Nginx's caching. I'll report it to the bug
Nginx's FastCGI caching used to work perfectly for me, but recently it
stopped working and I can't work out why.
This is how the headers look:
HTTP/1.1 200 OK
Server: nginx/1.2.7
Date: Sun, 03 Mar 2013 12:28:24 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 10727
Connection: keep-aliv
