trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leif Hedstrom (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TS-145) clarify cache.config actions in admin doc
Date Sat, 17 Apr 2010 04:09:30 GMT

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

Leif Hedstrom updated TS-145:
-----------------------------

    Fix Version/s: 2.1.0

> 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: Diane Smith
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message