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.
Attachments
Issue Links
- relates to
-
TS-3652 During 3xx redirect follow, TS uses the redirect url as the cache key ignoring any cache key set via API
-
- Closed
-