[openstreetmap-website] Turning off caching on /api/ endpoints w/ CORS (#220)
Tom MacWright
notifications at github.com
Mon Mar 25 15:00:20 UTC 2013
Right now some calls w/ oauth credentials are cached by the rails port and get a 304 response: confirm by logging in to
* http://osmlab.github.com/osm-auth/
* and then http://www.openstreetmap.us/iD/master/#layer=Bing&map=20.00/-77.02288/38.90081
The latter will get a 304 error until you clear your browser cache and you no longer send any cache-related headers.
Do we want caching on the endpoints? It's not clear how to fix this issue - have multiple web-based OAuth clients without conflicts - just from the JS side.
---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/220
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20130325/b2e37459/attachment.html>
More information about the rails-dev
mailing list