[
https://issues.apache.org/jira/browse/TS-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miles Libbey resolved TS-2429.
------------------------------
Resolution: Duplicate
Oops. Missed TS-145.
> cache.config clarification
> --------------------------
>
> Key: TS-2429
> URL: https://issues.apache.org/jira/browse/TS-2429
> Project: Traffic Server
> Issue Type: Improvement
> Components: Documentation
> Reporter: Miles Libbey
>
> The cache.config doc could use some clarification:
> - It is not clear to me what the difference between pin-in-cache and
> ttl-in-cache is -- when would you use one instead of the other. For
> instance, a clarifying remark might be,
> - 'Use pin-in-cache when you just want to override the server's TTL' or
> - 'Use pin-in-cache when you want to make sure all the requests for a
> domain are not evicted' or
> - 'use ttl-in-cache when a domain is not setting cache directives, but you
> want to cache anyway'
> - It's not clear to me when 'revalidate' would kick in. Does it only apply to
> objects that have cache-control headers?
> - I'd find it useful to have a few more combinations of examples:
> {don't know if these are valid syntax}
> # force a specific regex to be in cache between 7-11pm of the server's time.
> url_regex=example.com/articles/popular.* time=19:00-23:00 ttl-in-cache=1d2h
> # force all requests that would be sent to myorigin.com from 192.168.0/24 to
> not be cached
> dest_host=myorigin.com src_ip=192.168.0/24 action=never-cache
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
