[openstreetmap/openstreetmap-website] A Static (?) XML file can never receive a 304 Not Modified (#2264)
notifications at github.com
Sun Jun 16 22:33:36 UTC 2019
Conducting a simple refresh (f5) on a recently downloaded [test map page](https://www.openstreetmap.org/way/17236956) causes only half (10 out of 21) of the files to give a `304 Not Modified`.
Some of those files may well be dynamic, but some are clearly static. Because of the wide range of *Response Header* symptoms + my ignorance these are individual filetype reports to allow those with a working knowledge of the code to decipher it all. Please also note that since these tests the [`Last-Modified` value](https://github.com/openstreetmap/operations/issues/305) has been re-enabled & `eTag` disabled.
(probably) a static XML file. This is similar (but different) to the [HTML file problem](https://github.com/openstreetmap/operations/issues/306)
1 x XML
- `cache-control`: max-age=0, private, must-revalidate
- `eTag`: none
- `Expires`: none
- `Last-Modified`: none
- Request: (cache, but no `eTag` nor `Last-Modified`, so no request headers, so no 304)
The tiles supplied by *toothless* (eg https://b.tile.openstreetmap.org/18/130245/85447.png) are all dynamic yet all have a strong `eTag` (matched by the `If-None-Match`) + `Expires` + `Cache-Control` and thus get cached + a 304.
See bottom of [this Diary page](https://www.openstreetmap.org/user/alexkemp/diary/368814) for fuller details.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rails-dev