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
SPECIFICATION BUGS ONLY - Description =====================================
The "content-rewrite" feature allows a container to redirect links contained within a gadget through the container with optional caching. One of the params is "expires", which specifies the maximum length of time the container is permitted to cache the redirected content. Having the "expires" param here, however, contradicts and violates the standard HTTP Cache-Control mechanism, which defines the canonical standard for specifying how long an item is allowed to be cached. If the original source of the content does not wish it to be cached longer than a given period of time, then it should set an appropriate cache-control in the http response. Because of this, the "expires" param for the "content-rewrite" feature SHOULD be deprecated and eventually removed. If the developer truly wishes to maintain tight control over the caching of a resource, then they should exclude that resource from rewrite by using "exclude-url".
Document affected: ================== 1.) Please attach a patch for the document if appropriate. 2.) Post a thread at http://groups.google.com/group/opensocial-and-gadgets-spec/topics linking to this issue report. 3.) Post a comment on this issue, linking back to the thread.
Original author: [email protected] (May 11, 2012 23:37:39)
SPECIFICATION BUGS ONLY - Description
=====================================
The "content-rewrite" feature allows a container to redirect links contained within a gadget through the container with optional caching. One of the params is "expires", which specifies the maximum length of time the container is permitted to cache the redirected content. Having the "expires" param here, however, contradicts and violates the standard HTTP Cache-Control mechanism, which defines the canonical standard for specifying how long an item is allowed to be cached. If the original source of the content does not wish it to be cached longer than a given period of time, then it should set an appropriate cache-control in the http response. Because of this, the "expires" param for the "content-rewrite" feature SHOULD be deprecated and eventually removed. If the developer truly wishes to maintain tight control over the caching of a resource, then they should exclude that resource from rewrite by using "exclude-url".
Document affected:
==================
1.) Please attach a patch for the document if appropriate.
2.) Post a thread at
http://groups.google.com/group/opensocial-and-gadgets-spec/topics
linking to this issue report.
3.) Post a comment on this issue, linking back to the thread.
Original issue: http://code.google.com/p/opensocial-resources/issues/detail?id=1311
The text was updated successfully, but these errors were encountered: