[
https://issues.apache.org/jira/browse/TS-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275395#comment-15275395
]
ASF subversion and git services commented on TS-4020:
-----------------------------------------------------
Commit 3511a6630d00029d60e8c1728d7f06decabc0362 in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=3511a66 ]
TS-4020 Use cache-key URL for some plugins
cache_promote and background_fetch both use the pristine URL
as the hash for various internal lookup features. This works
well, except when it doesn't. For example, when mixed with
using the cachekey.so plugin.
This changes the behavior to use the cachekey URL. This is not
awesomely efficient at this point, but a future fix will use a
new API that allows introspection into the actual cache key used
by the ATS core instead.
> Cache_promote/background_fetch plugin LRU should use cachekey instead of url
> ----------------------------------------------------------------------------
>
> Key: TS-4020
> URL: https://issues.apache.org/jira/browse/TS-4020
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
> Reporter: Miles Libbey
> Assignee: Leif Hedstrom
> Labels: A
> Fix For: 7.0.0
>
>
> The Cache_promote plugin currently uses the URL when using the LRU policy.
> It would be better to use the cachekey, as that is actually going to be the
> index later.
> This would make any cachekey modifications also work for the promotion
> algorithm. For instance, if a domain has a (randomish) query string that gets
> removed for the cachekey, using the URL in the LRU would effectively never
> allow it to be promoted to cache, whereas the cachekey would.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
