[jira] [Resolved] (TS-3994) Internal Redirect follow should allow to use API set cache key.

["Sudheer Vinukonda (JIRA)" <ji...@apache.org>]

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

Sudheer Vinukonda resolved TS-3994.
-----------------------------------
    Resolution: Fixed

> 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
>             Fix For: 6.1.0
>
>
> 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)