[
https://issues.apache.org/jira/browse/TS-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995737#comment-14995737
]
Sudheer Vinukonda commented on TS-3994:
---------------------------------------
Note that as explained in
https://issues.apache.org/jira/browse/TS-3652?focusedCommentId=14571649&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14571649,
the cache open write actions during a redirect follow are no-ops, since the
cache_sm is still open on the original request's cache key. The change,
however, is needed in a lookup, since this will allow concurrent requests for
the same file to benefit/trigger RWW etc.
> Internal Redirect follow should allow to use API set cache key.
> ---------------------------------------------------------------
>
> Key: TS-3994
> URL: https://issues.apache.org/jira/browse/TS-3994
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Reporter: Sudheer Vinukonda
> Assignee: Sudheer Vinukonda
>
> Currently, during redirect follow, uses the Location header in the 3xx
> response as the cache key (and does not use the cache key set by using an
> API, for example).
> This can break the ability to serve cached response in some cases, where the
> redirect follow is performed (via a plugin to implement a simple fail-over
> mechanism between origin hosts, for example).
> Opening this jira to add a new configuration option to allow using original
> request cache key to lookup during redirect follow.
> This was briefly discussed in TS-3652, but, TS-3652 was actually tracking a
> different problem (turned out to be a regression) that prevents a redirect
> response being cached altogether.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
