You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2018/12/11 16:38:06 UTC

[GitHub] ocket8888 opened a new issue #3107: /api/1.3/origins has bad interactions with STEERING Delivery Services

ocket8888 opened a new issue #3107: /api/1.3/origins has bad interactions with STEERING Delivery Services
URL: https://github.com/apache/trafficcontrol/issues/3107
 
 
   Despite that an origin on a STEERING (or CLIENT_STEERING) Delivery Service is a more or less meaningless notion, it is perfectly acceptable to create an origin for those Delivery Services. Worse, creating an origin with (or modifying an existing one such that) `"isPrimary": true` on said Delivery Services - making an origin the 'primary' origin of that Delivery Service - will not only succeed nonsensically, but will also erroneously reply with a response body that shows `"isPrimary": true` is set on the origin, when it in fact is not. Further `GET`s to the `api/1.4/origins` endpoint will show `"isPrimary": false"`.
   
   The API should return a `400 BAD REQUEST` - or better yet a `422 UNPROCESSABLE ENTITY` - when a user attempts to create an origin assigned to a STEERING Delivery Service.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services