[
https://issues.apache.org/jira/browse/HTTPCORE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15462895#comment-15462895
]
Oleg Kalnichevski commented on HTTPCORE-431:
--------------------------------------------
bq. If content detection is out of scope, could we at least have
application/json entities decoded in UTF-8 by default? In fact, this was the
original change I was going to recommend.
@Paul:
Would that fix the immediate problem for you?
https://github.com/ok2c/httpcore/commit/df2c9805ca770691bed8b54c8cecb9e50ffaa3fc
> Correct character encoding default for application/json
> -------------------------------------------------------
>
> Key: HTTPCORE-431
> URL: https://issues.apache.org/jira/browse/HTTPCORE-431
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Components: HttpCore
> Reporter: Paul Draper
> Priority: Minor
>
> RFC 4627 and RFC 7159 require that parsers auto-detect the encoding of
> application/json. UTF-8 is the suggested default, though it's possible to
> detect the encoding of valid JSON unambiguously.
> Currently, EntityUtils.toString defaults to ISO-8859-1 (the default for text
> formats without a charset parameter).
> Given how common application/json is, it would be great for
> EntityUtils.toString to use the correct encoding.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
