You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Sudheer Vinukonda (JIRA)" <ji...@apache.org> on 2015/11/05 19:31:27 UTC
[jira] [Updated] (TS-3994) Internal Redirect follow should allow to
use API set cache key.
[ https://issues.apache.org/jira/browse/TS-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudheer Vinukonda updated TS-3994:
----------------------------------
Description:
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.
was:
Currently, during redirect follow, the cache key set by using an API for example. This breaks the ability to serve cached response in some cases, where the redirect follow is performed via a plugin.
Opening this jira to add a new configuration option to allow using original request cache key to lookup during redirect follow.
> 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)