OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Updated: (ODATA-283) Accept-Charset HTTP Request Header and charset content-type parameter

     [ http://tools.oasis-open.org/issues/browse/ODATA-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Drees updated ODATA-283:

Applied: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48762/odata-core-v4.0-wd01-part1-protocol-current-2013-4-5MP.docx

Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-283

  was:Applied: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48762/odata-core-v4.0-wd01-part1-protocol-current-2013-4-5MP.docx

> Accept-Charset HTTP Request Header and charset content-type parameter
> ---------------------------------------------------------------------
>                 Key: ODATA-283
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-283
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format, OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>             Fix For: V4.0_WD01
> The Accept-Charset request header is defined by RFC2616 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.2 ), so OData services SHOULD take it into account.
> On the other hand some JSON libraries issue requests with Accept: application/json;charset=utf-n, so OData services SHOULD take that into account, too.
> SHOULD is a pain for interoperability, so let's specify MUST.
> There are two ways to specify the charset, so we either have to force servers to reject conflicting statements, or define a precedence rule. The latter is friendlier, so we choose it.
> RFC2616 is a standard, and appending a format parameter to the media type is just a practice, so the Accept-Charset header takes precedence.
> The actual charset of a JSON payload can be determined from the first four octets (http://tools.ietf.org/html/rfc4627#section-3 ), so the format parameter is not necessary in the Content-Type header, and servers needn't include it. Again choice for servers is bad, so they MUST NOT include it.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]