[openstreetmap-website] Turning off caching on /api/ endpoints w/ CORS (#220)

[Tom Hughes]

I've applied d53bbe53f48d3f235ebc93af665ac912c057a51b to disable caching for CORS responses, which should fix the problem although it's rather ugly and I'm not at all clear that there shouldn't be a better solution...

The interesting thing is that the `304` response doesn't actually carry the CORS response headers so the browser couldn't use them even if wanted to. They are getting returned from the ruby part of passenger to the C part though, and I don't think the C part is eating them, so I think the apache core must be discarding them for some reason.

In any case I have been unable to find any discussion anywhere of how CORS and caching and conditional gets are supposed to interact so I really don't know what _should_ be happening here.

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/220#issuecomment-15429732
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20130325/0c70ceef/attachment.html>