Re: Obsolete Traffic Ops API endpoint removal

+1 on removing the route. I would like to see our downstream components migrate to something different than the giant monolithic JSON configuration instead of moving to this new endpoint which is essentially the same format minus some key information. I agree with what Rob said; it was an

Re: Obsolete Traffic Ops API endpoint removal

Hey Rawlin, I took a look through our splunk logs and it looks like we don't have anything at Comcast that has hit that endpoint in the last 90 days. For this reason, I am +1 on removing. Thanks, Dave On Thu, Jul 6, 2017 at 11:27 AM, Robert Butts wrote: > This isn't

Obsolete Traffic Ops API endpoint removal

Hey all, I believe I’ve found an obsolete/broken API endpoint [1] that might be a good candidate for removal. Here is an example request: GET /api/1.2/cdns/mycdn/configs/routing This will return a json object that looks like the following: { “response”: { “trafficServers”: […],