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

For the "content-rewrite" feature, the "expires" param inappropriately supersedes normal Cache-control mechanisms #1289

Open
mmarum-sugarcrm opened this issue Jun 5, 2013 · 0 comments

Comments

@mmarum-sugarcrm
Copy link
Member

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

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

No branches or pull requests

1 participant