When using query string URL signing, if the client adds any additional query strings to the URL, these are ALWAYS considered in the URL hash regardless of the use parts settings.
When using pathparams URL signing, if the client adds query string parameters to the URL they are NEVER considered in the URL hash regardless of the use parts settings.
Provide a signing option which allows users to override the default behavior and include or exclude custom query strings in the URL signature hash. Standard behavior could remain as is and this new parameter would allow users to override the standard behavior.
Is this still an issue - especially now that Consistent Hashing Query Parameters have been introduced? Which kind of hashing are you talking about, Traffic Router or Traffic Server?
When using query string URL signing, if the client adds any additional query strings to the URL, these are ALWAYS considered in the URL hash regardless of the use parts settings.
When using pathparams URL signing, if the client adds query string parameters to the URL they are NEVER considered in the URL hash regardless of the use parts settings.
Provide a signing option which allows users to override the default behavior and include or exclude custom query strings in the URL signature hash. Standard behavior could remain as is and this new parameter would allow users to override the standard behavior.
Author: Ryan Durfey JIRA Link: https://issues.apache.org/jira/browse/TC-153 Found Version: 2.1.0