You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This Bug Report affects these Traffic Control components:
Traffic Ops
Current behavior:
After #7023 was merged, some endpoints that return the represenation of a server in the response don't have the ASN field accounted for. These routes will need a 4.1 api version equivalent, so that these new routes can account for the new field.
Expected behavior:
All 3.1 routes should return a consistent representation of a server object.
Steps to reproduce:
Except for the GET /api/4.1/servers endpoint, all other 4.1 routes return a server representation that does not have the asns field in it. This needs to be fixed so that all routes return the same server object representation.
This Bug Report affects these Traffic Control components:
Current behavior:
After #7023 was merged, some endpoints that return the represenation of a server in the response don't have the ASN field accounted for. These routes will need a
4.1api version equivalent, so that these new routes can account for the new field.Expected behavior:
All 3.1 routes should return a consistent representation of a server object.
Steps to reproduce:
Except for the
GET /api/4.1/serversendpoint, all other 4.1 routes return a server representation that does not have theasnsfield in it. This needs to be fixed so that all routes return the same server object representation.