id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	uname	nginx_version
928	Can't use If-Modified-Since with http://nginx.org/en/CHANGES	Bruno Bigras		"I'm not sure it it's a bug. And it's a minor thing so you may not care about it.

I'm trying to track http://nginx.org/en/CHANGES to be notified when there's a new release (an RSS feed would be nice) and I'm saving Last-Modified and the ETag expecting to get a '304 not modified' on the next fetch and save a tiny bit of bandwitdh.

Today if I run 'curl -I http://nginx.org/en/CHANGES' multiple times I get two differents Last-Modified and etag so I can't use 'If-Modified-Since' and 'If-None-Match'.

$ curl -I http://nginx.org/en/CHANGES
HTTP/1.1 200 OK
Server: nginx/1.9.12
Date: Wed, 09 Mar 2016 21:26:01 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 259440
Last-Modified: Wed, 24 Feb 2016 15:10:05 GMT
Connection: keep-alive
Keep-Alive: timeout=15
ETag: ""56cdc7cd-3f570""
Accept-Ranges: bytes

$ curl -I http://nginx.org/en/CHANGES
HTTP/1.1 200 OK
Server: nginx/1.9.12
Date: Thu, 10 Mar 2016 20:15:40 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 259440
Last-Modified: Wed, 24 Feb 2016 15:10:14 GMT
Connection: keep-alive
Keep-Alive: timeout=15
ETag: ""56cdc7d6-3f570""
Accept-Ranges: bytes"	defect	closed	minor		other	1.9.x	fixed				not applicable