Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we be returning Last-Modified on single-element calls? #36

Closed
pnorman opened this issue Jul 30, 2013 · 2 comments
Closed

Should we be returning Last-Modified on single-element calls? #36

pnorman opened this issue Jul 30, 2013 · 2 comments
Milestone

Comments

@pnorman
Copy link
Contributor

pnorman commented Jul 30, 2013

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.

This was referenced Jul 31, 2013
@pnorman
Copy link
Contributor Author

pnorman commented Sep 9, 2013

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.

@zerebubuth
Copy link
Owner

OK. We can always come back to this later if it looks like it's important for some use-case.

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

No branches or pull requests

2 participants