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/09/27 14:49:33 UTC

[GitHub] ocket8888 opened a new issue #2881: Some API Responses use wrong Content-Type

ocket8888 opened a new issue #2881: Some API Responses use wrong Content-Type
URL: https://github.com/apache/trafficcontrol/issues/2881
 
 
   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.

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