[TS-4025] Consistent hashing in parent.config can use suboptimal URL for hash

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 7.1.0
• Component/s: Parent Proxy
• Assignee: John Rushford
• Reporter: Leif Hedstrom
• Created: 16/Nov/15 18:08
• Updated: 08/Sep/16 15:39

Description

In a setup, where the same assets can have different URLs (e.g. query parameters, or two paths normalized to the same cache key), parent proxy can be suboptimal. This is TS-4020, and the solutions would be similar; Use the cache key (CacheInfo->md5) which is internally what we call LookupURL. LookupURL is that URL that plugins modify to change the cache key.

This has to be rolled out carefully as well, we're thinking something like

6.x - We add a new configuration, that lets you use the LookupURL for the hash (default off)

7.x - We change this new configuration to be enabled by default

8.x - We remove this configuration.

This Jira tracks the first step, we'll file subsequent Jira's for 7.x and 8.x.

Issue Links

• relates to: TS-4030 Add option to remove query string from URL hashing in consistent hash parent selection method.