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 2015/03/18 14:02:38 UTC
[jira] [Updated] (OLINGO-594) Json content type header without
charset encoding might lead to issues
[ https://issues.apache.org/jira/browse/OLINGO-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Amend updated OLINGO-594:
-----------------------------------
Description:
Olingo does not set the charset parameter for the content type application/json as per specification.
This might lead to issues with clients that do not follow the specification and expect a charset parameter.
After an initial investigation it might be that the library does not encode the json payload in UTF-8 anyway. So we have to check this and decide how to work with noncompliant clients.
was:
Olingo does not set the charset parameter for the content type application/json as per specification.
This might lead to issues with clients that do not follow the specification and expect a charset parameter.
After an initial investigation it might be that the library does not encode the json payload in UTF-8 nayway. So we have to check this.
> Json content type header without charset encoding might lead to issues
> ----------------------------------------------------------------------
>
> Key: OLINGO-594
> URL: https://issues.apache.org/jira/browse/OLINGO-594
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core
> Affects Versions: V2 2.0.3
> Reporter: Christian Amend
> Assignee: Christian Amend
> Fix For: V2 2.0.4
>
>
> Olingo does not set the charset parameter for the content type application/json as per specification.
> This might lead to issues with clients that do not follow the specification and expect a charset parameter.
> After an initial investigation it might be that the library does not encode the json payload in UTF-8 anyway. So we have to check this and decide how to work with noncompliant clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)