-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_ERRATA02
-
Fix Version/s: V4.0_ERRATA03
-
Component/s: Protocol
-
Labels:None
-
Environment:
Applied
-
Proposal:
-
Resolution:
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).