You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rails report returns a Last-Modified header to /(node|way|relation)/# queries. Should we do the same in cgimap? I am not currently testing for this in my integration tests as I am stopped from time testing by openstreetmap/openstreetmap-website#375 and the related osmosis bug
Note: the rails port doesn't return one for /way/#/full queries.
I'm not sure how useful this header is, given we don't support HEAD requests in cgimap and for a single element query you basically have to do all the work to get the date anyways.
In any case, we should decide one way or the other.
The text was updated successfully, but these errors were encountered:
I'm okay with wontfix'ing this. Given that a HEAD request involves the same load on the DB server, we don't really want people to make use of them, and the rails port doesn't provide Last-Modified on other calls.
The rails report returns a
Last-Modified
header to /(node|way|relation)/# queries. Should we do the same in cgimap? I am not currently testing for this in my integration tests as I am stopped from time testing by openstreetmap/openstreetmap-website#375 and the related osmosis bugNote: the rails port doesn't return one for /way/#/full queries.
I'm not sure how useful this header is, given we don't support HEAD requests in cgimap and for a single element query you basically have to do all the work to get the date anyways.
In any case, we should decide one way or the other.
The text was updated successfully, but these errors were encountered: