You can clone with
HTTPS or Subversion.
Currently, when you set a json body using the json property the following headers are added to your request.
The content-type lacks a charset, which I believe the http rfc says should be treated as ISO-8859-1.
Thoughts on either adding a charset=utf-8 like on the form bodies or opening up some way to set the charset?
Happy to do a PR for you, just wanted to know your thoughts on the best approach.
Quite the contrary, RFC 4627 does not define a charset parameter because it requires that JSON is always encoded in Unicode. Perhaps you are thinking of section 3.7.1 of RFC 2616 which defines ISO-8859-1 as the default for subtypes of the "text" type (of which application/json is not)?
this also came up in a new thread and i'm more worried about breaking dumb checks for application/json than I am in breaking the few out of spec implementations that require this.