Personally I'd like to see this accompanied by an official deprecation for the "reserved" Query Parameters used by Traffic Router
Is there someone out there using query parameters like e.g. `format` and `fakeClientIPAddress` who would for some reason be unable to use HTTP Headers instead? ________________________________________ From: Dan Kirkwood <[email protected]> Sent: Monday, May 6, 2019 4:54 PM To: [email protected] Subject: [EXTERNAL] new feature: Consistent Hash with Query Parameters Hi all.. I've just submitted a PR as a draft - https://github.com/apache/trafficcontrol/pull/3552 that adds a new field to a deliveryservice. `consistentHashQueryParams` lists the query parameter keys that may be used on a deliveryservice to be included in addition to the url path when the consistent hash value is calculated. This would allow, for example, the same path to be used for an asset in a different format, but not require the same cache to be used for each. I submitted as a draft for now to allow testing on it. Right now, the db, traffic ops, and traffic router changes are included. Traffic portal changes are to follow. Comment welcome.. Dan
