[TS-3652] During 3xx redirect follow, TS uses the redirect url as the cache key ignoring any cache key set via API

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Component/s: HTTP
• Assignee: Sudheer Vinukonda
• Reporter: Sudheer Vinukonda
• Created: 01/Jun/15 21:20
• Updated: 08/Nov/15 18:12
• Resolved: 03/Jun/15 21:48

Description

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.

Issue Links

• is related to: TS-3661 Cache broken during 3xx redirect follow response
• is related to: TS-3994 Internal Redirect follow should allow to use API set cache key.