Dan Morgan created TS-3374:
------------------------------
Summary: Issues with cache.config implementation
Key: TS-3374
URL: https://issues.apache.org/jira/browse/TS-3374
Project: Traffic Server
Issue Type: Bug
Components: Cache
Reporter: Dan Morgan
The documentation implies that entries in the cache.config file are processed
in 'order'.
For example, this example in the docs:
---------------------------------------------------------------
The following example configures Traffic Server to revalidate gif and jpeg
objects in the domain mydomain.com every 6 hours, and all other objects in
mydomain.com every hour. The rules are applied in the order listed.
dest_domain=mydomain.com suffix=gif revalidate=6h
dest_domain=mydomain.com suffix=jpeg revalidate=6h
dest_domain=mydomain.com revalidate=1h
---------------------------------------------------------------
However, running with version 5.1.2 and having the following lines:
dest_domain=mydomain.com prefix=somepath suffix=js revalidate=7d
dest_domain=mydomain.com suffix=js action=never-cache
I would expect it to not cache any .js URL's from mydomain.com, except those
that have a prefix of 'somepath'. However what happens is that the
action=never-cache is applied to all URL's having mydomain.com (even the ones
that have a prefix of 'somepath').
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
