Is this compliant by default? RFC 2616 says the server shouldn't return 200 if the variant is unmodified since IMS?
Anyway, as long as it is configurable. Thanks!
Kind regards,
Fredrik
-----Original Message-----
From: nginx-bounces@nginx.org [mailto:nginx-bounces@nginx.org] On Behalf Of Valentin V. Bartenev
Sent: den 15 maj 2012 12:36
To: nginx@nginx.org
Subject: Re: If-Modified-Since
On Tuesday 15 May 2012 13:29:00 Fredrik Widlund wrote:
> Hi,
>
> I'm obviously losing it somehow. What am I missing here, it must be
> something obvious that is going to make me look stupid, but I still
> don't see it. I just can't get If-Modified-Since to work?
>
> Linux poc 3.3.4-2-ARCH #1 SMP PREEMPT Wed May 2 18:28:42 CEST 2012
> x86_64
> Intel(R) Xeon(R) CPU E5540 @ 2.53GHz GenuineIntel GNU/Linux
>
> Default configure/make/nginx.conf etc directly from the 1.2.0 dist.
>
> I send an IMS header, later than the last-modified, and still get a 200?
>
> x@poc> touch a
> x@poc> curl -za -v localhost/index.html
> * About to connect() to localhost port 80 (#0)
> * Trying 127.0.0.1...
> * connected
> * Connected to localhost (127.0.0.1) port 80 (#0)
>
> > GET /index.html HTTP/1.1
> > User-Agent: curl/7.25.0 (x86_64-unknown-linux-gnu) libcurl/7.25.0
> > OpenSSL/1.0.1b zlib/1.2.7 libssh2/1.4.0 Host: localhost
> > Accept: */*
> > If-Modified-Since: Tue, 15 May 2012 11:18:36 GMT
>
> < HTTP/1.1 200 OK
> < Server: nginx/1.2.0
> < Date: Tue, 15 May 2012 11:18:40 GMT
> < Content-Type: text/html
> < Content-Length: 151
> < Last-Modified: Tue, 15 May 2012 11:17:22 GMT < Connection:
> keep-alive < Accept-Ranges: bytes [...]
[...]
http://nginx.org/r/if_modified_since
default: if_modified_since exact;
And here is explained why: http://trac.nginx.org/nginx/ticket/93
wbr, Valentin V. Bartenev
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
