When you make a call to a 3.x API endpoint that returns a server object, you get back a version 4.0 specific server representation. This breaks compatibility with clients that are using the 3.x version.
This Bug Report affects these Traffic Control components:
Current behavior:
Make a call to a version 3.x endpoint like PUT servers/{id} to update an existing server, and notice the server object that you get back in the response. This is a version 4.0 server object.
Expected behavior:
The returned server object should be consistent with the API version that is being requested by the client.
Steps to reproduce:
Make a call to a version 3.x endpoint like PUT servers/{id} to update an existing server, and notice the server object that you get back in the response. This is a version 4.0 server object.
When you make a call to a 3.x API endpoint that returns a server object, you get back a version 4.0 specific server representation. This breaks compatibility with clients that are using the 3.x version.
This Bug Report affects these Traffic Control components:
Current behavior:
Make a call to a version 3.x endpoint like
PUT servers/{id}to update an existingserver, and notice theserverobject that you get back in the response. This is a version 4.0serverobject.Expected behavior:
The returned
serverobject should be consistent with the API version that is being requested by the client.Steps to reproduce:
Make a call to a version 3.x endpoint like
PUT servers/{id}to update an existingserver, and notice theserverobject that you get back in the response. This is a version 4.0serverobject.