Open elsloo opened 5 years ago
This appears to be a duplicate of a JIRA issue that @mtorluemke created in 2016 which was copied here into GitHub as #960.
Ha! Mark knew 3 years ago what we now really need today. Which issue do you want to keep, @elsloo?
Currently in Traffic Portal (and Ops), we have one dropdown to control query string handling. This dropdown controls the way query strings are handled both with the cache key and with parent selection. This behavior should be separated into two distinct functions: one that controls the way that the query string is handled with parent selection and another that relates to cache key. This would allow for independent configuration, but also more robust cache key configurations via delivery service profiles or raw remap text. Currently, a cache key configuration is placed on the remap line when the value is set to > 0, and consequently, any additional cache key configuration through the aforementioned mechanisms may have no effect due to the ordering dependencies within ATS.