You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Christian Amend (JIRA)" <ji...@apache.org> on 2016/03/03 12:16:18 UTC

[jira] [Resolved] (OLINGO-896) $format=json does not set Content-Type with Character set utf-8

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

Christian Amend resolved OLINGO-896.
------------------------------------
    Resolution: Won't Fix
      Assignee: Christian Amend

The RFC does not define a charset parameter for the application/json content type (http://tools.ietf.org/html/rfc7159#page-11)

Quote: No "charset" parameter is defined for this registration.
      Adding one really has no effect on compliant recipients.

Olingo sends the response UTF-8 encoded but uncompliant recipients might not display this data correctly.

If you disagree with this please reopen the issue.

> $format=json does not set Content-Type with Character set utf-8
> ---------------------------------------------------------------
>
>                 Key: OLINGO-896
>                 URL: https://issues.apache.org/jira/browse/OLINGO-896
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-core
>    Affects Versions: V2 2.0.4
>            Reporter: Girish Sainath
>            Assignee: Christian Amend
>
> Hi,
> When $format=json is in the get request then the Content-Type is set to "application/json" and the Character set "utf-8" is not added. So non-ascii characters and umlauts are not returned properly in the response data.
> For Example : "München" is returned as "MÃ¼nchen"
> Regards
> Girish



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)