Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

API should provide Last-Modified HTTP header #578

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Closed

API should provide Last-Modified HTTP header #578

openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments

Comments

@openstreetmap-trac
Copy link

Reporter: openstreetmap[at]firefishy.com
[Submitted to the original trac issue database at 11.36am, Tuesday, 30th October 2007]

The API should provide the Last-Modified HTTP header.

Last-Modified header definition:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.29

I would also recommend adding the following HTTP header to avoid potential caching problems:
Cache-Control: s-maxage=0, max-age=0, must-revalidate, proxy-revalidate

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 10.04am, Wednesday, 31st October 2007]

Um... why? The cache-control maybe, but last-modified? It would be major pain in the arse to compute for at least some api calls and I don't see any benefit.

@openstreetmap-trac
Copy link
Author

Author: steve[at]fractalus.com
[Added to the original trac issue at 5.44pm, Monday, 21st January 2008]

fixed in nodes, ways and relations

@openstreetmap-trac
Copy link
Author

Author: rjmunro[at]arjam.net
[Added to the original trac issue at 11.38pm, Monday, 21st January 2008]

Fixed in [6524].

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant