[OASIS Issue Tracker] (ODATA-908) 8.1.1 Header Content-Type: is only SHOULD in RFC7231

[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 ]

Michael Pizzo updated ODATA-908:
--------------------------------

    Description: 
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).




  was:
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

       Proposal: 
While we can be more restrictive in OData by requiring the Content-Type header in responses, we want to allow for cases where the upload client doesn't specify a content-type. 

Therefore, we should change Content-type from MUST to SHOULD for media types. This allows a service to return content received with no content type as either application/octet-stream or without a content type.

  was:Replace MUST with SHOULD.


> 8.1.1 Header Content-Type: is only SHOULD in RFC7231
> ----------------------------------------------------
>
>                 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
>             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)