[
https://issues.apache.org/jira/browse/HTTPCORE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15458171#comment-15458171
]
Paul Draper edited comment on HTTPCORE-431 at 9/2/16 10:33 AM:
---------------------------------------------------------------
GitHub pull request: https://github.com/apache/httpcore/pull/30
Sorry about the initial branch mixup on the PR....it's been fixed now.
{code}
commit 62085d757f13306c51820e593652cbd3f4340cd7
Author: Paul Draper <p...@lucidchart.com>
Date: Fri Sep 2 04:18:53 2016 -0600
HTTPCORE-431 Correct default encoding for application/json
Auto-detect UTF encoding as described in RFC 4627/7159, including BOM
handling
{code}
was (Author: draperp):
GitHub pull request: https://github.com/apache/httpcore/pull/30
> 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: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
