Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some API Responses use wrong Content-Type #2881

Closed
ocket8888 opened this issue Sep 27, 2018 · 1 comment · Fixed by #5369
Closed

Some API Responses use wrong Content-Type #2881

ocket8888 opened this issue Sep 27, 2018 · 1 comment · Fixed by #5369
Labels
bug something isn't working as intended low impact affects only a small portion of a CDN, and cannot itself break one Traffic Ops related to Traffic Ops

Comments

@ocket8888
Copy link
Contributor

The only concrete example with which I can come up is /api/1.3/servers/<hostname>/configfiles/ats, which responds with Content-Type: text/plain;charset=UTF-8, which is the correct character encoding, but the data is a JSON object so this header should be Content-Type: application/json;charset=UTF-8. However, I seriously doubt that out of all of TO's hundreds of API endpoints, this is the only one to suffer from this header issue.

@rawlinp rawlinp added bug something isn't working as intended Traffic Ops API labels Sep 27, 2018
@mitchell852 mitchell852 added Traffic Ops related to Traffic Ops and removed Traffic Ops related to Traffic Ops Traffic Ops API labels Oct 17, 2018
@mitchell852 mitchell852 added the low impact affects only a small portion of a CDN, and cannot itself break one label Dec 8, 2020
@zrhoffman
Copy link
Member

/api/3.0/ping still returns the wrong content type as of d4780c3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended low impact affects only a small portion of a CDN, and cannot itself break one Traffic Ops related to Traffic Ops
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants