ocket8888 opened a new pull request, #7405:
URL: https://github.com/apache/trafficcontrol/pull/7405

   This PR fixes #6385 by causing Traffic Ops to return the correct error code 
(400 Bad Request) and an alert describing what went wrong when a client 
attempts to create or modify a Delivery Service such that it would an entry in 
its Consistent Hashing Query string Parameters that is reserved for use by 
Traffic Router.
   
   <hr/>
   
   ## Which Traffic Control components are affected by this PR?
   - Traffic Ops
   
   ## What is the best way to verify this PR?
   ```bash
   topost -kp deliveryservices '{       
           "active": false,
           "cdnId": 2,
           "consistentHashQueryParams": ["format"],
           "displayName": "test",
           "dnsBypassCname": "test",
           "dscp": 1,
           "geoLimit": 1,
           "geoLimitCountries": "US,CA",
           "geoProvider": -7,
           "initialDispersion": 1,
           "ipv6RoutingEnabled": true,
           "logsEnabled": true,
           "missLat": 0,
           "missLong": 0,
           "multiSiteOrigin": false,
           "orgServerFqdn": "test.quest",
           "protocol": 7,
           "qstringIgnore": 5,
           "rangeRequestHandling": 0,
           "regionalGeoBlocking": false,
           "tenantId": 1,
           "typeId": 1,
           "xmlId": "test"
   }'
   ```
   
   ## If this is a bugfix, which Traffic Control versions contained the bug
   - not sure
   
   
   ## PR submission checklist
   - [x] This PR has tests <!-- If not, please delete this text and explain why 
this PR does not need tests. -->
   - [x] This PR has documentation <!-- If not, please delete this text and 
explain why this PR does not need documentation. -->
   - [x] This PR has a CHANGELOG.md entry <!-- A fix for a bug from an ATC 
release, an improvement, or a new feature should have a changelog entry. -->
   - [x] This PR **DOES NOT FIX A SERIOUS SECURITY VULNERABILITY**


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to