[
https://issues.apache.org/jira/browse/TS-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569197#comment-14569197
]
Leif Hedstrom commented on TS-3652:
-----------------------------------
Talking to @amc, assuming this is only an issue when a) a plugin is modifying
the cache key and b) the server is setup to follow the redirect, I agree with
amc. I think we need to have the plugin modify the cache key a second time
(before following the redirect) in this very special case.
I'm also making an assumption that following the redirect does not go through
remap.config? If it did, then things changes again, because then I'd expect
normal cache key modifications to happen as part of remapping. Finally, if this
were to happen without a plugin modifying the cache key, then we definitely
have a core bug, but it sounds like that doesn't happen?
> During 3xx redirect follow, TS uses the redirect url as the cache key
> ignoring any cache key set via API
> --------------------------------------------------------------------------------------------------------
>
> Key: TS-3652
> URL: https://issues.apache.org/jira/browse/TS-3652
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Sudheer Vinukonda
>
> Currently, during 3xx redirect follow, TS uses the redirect url (as received
> in the *Location* header of the 3xx response) as the cache key for storing
> the subsequent response to the redirect follow request. This works fine in
> most cases, since, the original client request would have cached the 3xx
> response and the final response would still be derived using the redirect
> follow url. This also allows direct requests to the redirect follow location
> be served from the cache efficiently.
> However, this is not desirable in some cases, especially when there's a TS
> API (plugin) modifying the cache key and wanting to store the final response
> against the modified cache key directly.
> Proposing to add a config setting to allow storing API set cache key during
> redirect follow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
