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/04/19 17:53:26 UTC

[GitHub] dg4prez commented on issue #1595: Traffic Ops update_status endpoint returns empty response without use_reval_pending parameter set in global profile

dg4prez commented on issue #1595: Traffic Ops update_status endpoint returns empty response without use_reval_pending parameter set in global profile
URL: https://github.com/apache/incubator-trafficcontrol/issues/1595#issuecomment-382825008
 
 
   It looks to me like the go version of the API is returning a value for reval_pending and parent_reval_pending regardless of the status or existence of use_reval_pending in global.  This is not how the 1.2 api functioned, nor is it how ORT functions - if the parameter exists, it assumes that reval_pending is in use and does not check revalidation status.  This will absolutely break invalidation unless reval pending is actually enabled.  For backwards compatibility, the API needs to be updated to remove this value from the json, or we need to modify the ort script to change how it functions.

----------------------------------------------------------------
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