[openstreetmap-website] Cache-Control on API GET calls (#337)

[pnorman]

Currently the API sends a ``Cache-Control: max-age=0, private, must-revalidate`` header in node responses. [RFC2616](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1) gives the meaning of private as

> Indicates that all or part of the response message is intended for a single user and MUST NOT be cached by a shared cache. This allows an origin server to state that the specified parts of the response are intended for only one user and are not a valid response for requests by other users. A private (non-shared) cache MAY cache the response.

whereas public is
> Indicates that the response MAY be cached by any cache, even if it would normally be non-cacheable or cacheable only within a non- shared cache. (See also Authorization, section 14.8, for additional details.)

Given the nature of the GET API calls, public seems like a better fit.


---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/337
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20130715/c1e515ec/attachment.html>