[jira] [Resolved] (TS-145) clarify cache.config actions in admin doc

["Miles Libbey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miles Libbey resolved TS-145.
-----------------------------

    Resolution: Fixed

https://github.com/apache/trafficserver/commit/8e02b12c204c1ab9647b3e4505d3aa9da9159def#diff-9a09b4dfda82e3e665e31092d1c3ec8d

Thanks to chatting with Leif....

> clarify cache.config actions in admin doc
> -----------------------------------------
>
>                 Key: TS-145
>                 URL: https://issues.apache.org/jira/browse/TS-145
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Miles Libbey
>            Assignee: Miles Libbey
>            Priority: Minor
>             Fix For: Docs
>
>
> The differences between the actions in http://incubator.apache.org/trafficserver/docs/admin/files.htm#48049 don't seem very clear to me.  I don't understand the difference between:
> pin-in-cache
> revalidate
> ttl-in-cache
> Perhaps we could explain what different behaviors would happen if these settings (individually) entered
> url_regex=example.com/documents/article\d+.html pin-in-cache=6h 
> url_regex=example.com/documents/article\d+.html revalidate=6h 
> url_regex=example.com/documents/article\d+.html ttl-in-cache=6h 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)