[jira] [Commented] (TS-965) cache.config can't deal with both revalidate= and ttl-in-cache= specified
[ https://issues.apache.org/jira/browse/TS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421281#comment-15421281 ] Bryan Call commented on TS-965: --- [~jsime] Can you please clarify how cache.config settings interact? > cache.config can't deal with both revalidate= and ttl-in-cache= specified > - > > Key: TS-965 > URL: https://issues.apache.org/jira/browse/TS-965 > Project: Traffic Server > Issue Type: Bug > Components: Documentation >Affects Versions: 3.1.0, 3.0.1 >Reporter: Igor Galić >Assignee: Jon Sime > Labels: A, cache-control > Fix For: sometime > > > If both of these options are specified (with the same time?), nothing is > cached at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-965) cache.config can't deal with both revalidate= and ttl-in-cache= specified
[ https://issues.apache.org/jira/browse/TS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14582159#comment-14582159 ] Bryan Call commented on TS-965: --- Make ttl-in-cache= like the DNS TTL where you can have a min, max, and override. cache.config can't deal with both revalidate= and ttl-in-cache= specified - Key: TS-965 URL: https://issues.apache.org/jira/browse/TS-965 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 3.1.0, 3.0.1 Reporter: Igor Galić Assignee: Alan M. Carroll Labels: A, cache-control Fix For: 6.2.0 If both of these options are specified (with the same time?), nothing is cached at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-965) cache.config can't deal with both revalidate= and ttl-in-cache= specified
[ https://issues.apache.org/jira/browse/TS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14352036#comment-14352036 ] Zhao Yongming commented on TS-965: -- I have no idea of what is the detail, as cache.config is a multi-matching rule system, and there is some hard-coded rules which is not explained anywhare, for example: if you matched with 'no-cache', then it will not cache. I don't like the idea with the cache-control matching, which is hard to extend and hard to use in real world, maybe we should avoid using it in fever of the LUA remaping and LUA plugins cache.config can't deal with both revalidate= and ttl-in-cache= specified - Key: TS-965 URL: https://issues.apache.org/jira/browse/TS-965 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 3.1.0, 3.0.1 Reporter: Igor Galić Assignee: Alan M. Carroll Labels: A, cache-control Fix For: 5.3.0 If both of these options are specified (with the same time?), nothing is cached at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TS-965) cache.config can't deal with both revalidate= and ttl-in-cache= specified
[ https://issues.apache.org/jira/browse/TS-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13757974#comment-13757974 ] Leif Hedstrom commented on TS-965: -- We should investigate this for v4.1.0 cache.config can't deal with both revalidate= and ttl-in-cache= specified - Key: TS-965 URL: https://issues.apache.org/jira/browse/TS-965 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 3.1.0, 3.0.1 Reporter: Igor Galić Labels: A Fix For: 4.1.0 If both of these options are specified (with the same time?), nothing is cached at all. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira