hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HTTPCORE-431) Correct character encoding default for application/json
Date Mon, 05 Sep 2016 18:57:20 GMT

     [ https://issues.apache.org/jira/browse/HTTPCORE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Kalnichevski resolved HTTPCORE-431.
----------------------------------------
       Resolution: Fixed
    Fix Version/s: 5.0-alpha2
                   4.4.6

Patch committed to SVN trunk and 4.4.x branch.

Oleg

> 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
>             Fix For: 4.4.6, 5.0-alpha2
>
>
> 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-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message