You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by danobi <gi...@git.apache.org> on 2017/02/23 20:13:30 UTC
[GitHub] trafficserver issue #1484: There should be a Cache-Control immutable constan...
GitHub user danobi opened an issue:
https://github.com/apache/trafficserver/issues/1484
There should be a Cache-Control immutable constant in the API
We could call it `TS_HTTP_VALUE_IMMUTABLE`.
See https://tools.ietf.org/html/draft-mcmanus-immutable-01 for the RFC draft.
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] trafficserver issue #1484: There should be a Cache-Control immutable constan...
Posted by zwoop <gi...@git.apache.org>.
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1484
Well, more than just having the constant, we really need to think about the implications of this, and how we should handle immutable in the cache. Today, we have configurations to basically achieve "immutable", such that clients can't force a refresh. Interacting with this new CC: immutable would give this control back to the origin server instead of configurations on ATS (which is a good thing, at least in reverse proxies).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---