You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2015/11/16 19:09:11 UTC
[jira] [Created] (TS-4025) Consistent hashing in parent.config can
use suboptimal URL for hash
Leif Hedstrom created TS-4025:
---------------------------------
Summary: Consistent hashing in parent.config can use suboptimal URL for hash
Key: TS-4025
URL: https://issues.apache.org/jira/browse/TS-4025
Project: Traffic Server
Issue Type: Bug
Components: Parent Proxy
Reporter: Leif Hedstrom
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)