[OASIS Issue Tracker] (ODATA-908) Header Content-Type shouldn't be required for media types

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Ralf Handl updated ODATA-908:
-----------------------------

    Resolution: 
Applied to 8.1.1 Header Content-Type

https://www.oasis-open.org/committees/download.php/57689/odata-v4.0-wd08-part1-protocol-2016-03-03.docx

  was:Applied to 8.1.1 Header Content-Type


> Header Content-Type shouldn't be required for media types
> ---------------------------------------------------------
>
>                 Key: ODATA-908
>                 URL: https://issues.oasis-open.org/browse/ODATA-908
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>         Environment: Proposed
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>             Fix For: V4.0_ERRATA03
>
>
> This section misquotes RFC7231 and states that a Content-Type header MUST be present.
> https://tools.ietf.org/html/rfc7231#section-3.1.1.5 only says SHOULD
> Note that browsers may not specify a content type in some cases. This means that a client can upload a media type without specifying a content-type, the service can store it, and then return the media in a response but may not know what the content-type is (server could return application/octet-stream).



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)