Jira (PUP-7261) Add/Honor charset parameter in Content-Type header

[Josh Cooper (JIRA)]

Title: Message Title

Josh Cooper commented on PUP-7261   Re: Add/Honor charset parameter in Content-Type header Strictly speaking the charset is redundant because json parsers are supposed to detect the encoding, UTF-8, UTF-16 (BE or LE) , UTF-32 (BE or LE), based on the presences of null bytes in the first 4 octets, see https://www.ietf.org/rfc/rfc4627.txt, section 3 Encoding. But in practice, both google and github include the following charset: curl -i https://api.github.com/users/joshcooper HTTP/1.1 403 Forbidden Server: GitHub.com Date: Wed, 08 Mar 2017 00:22:23 GMT Content-Type: application/json; charset=utf-8 curl -i https://www.googleapis.com/customsearch/v1 HTTP/1.1 400 Bad Request Vary: X-Origin Content-Type: application/json; charset=UTF-8 So I'd recommend we always respond in UTF-8 and we always add Content-Type: application/json; charset=utf-8. And according to http://www.iana.org/assignments/character-sets/character-sets.xhtml, charsets are case-insensitive, so either UTF-8 or utf-8 is allowed, but we should pick one. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.