Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-1457

Potential confusion wrt Content-Type header for media entities

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: V4.01_OS
    • Fix Version/s: V4.02
    • Component/s: Protocol
    • Labels:
      None
    • Proposal:
      Hide

      Relax our requirement, and as such be consistent, about the requirement of having to provide a Content-Type header in requests creating and updating media entities, and as such be no stricter then the HTTP specification itself either.

      Show
      Relax our requirement, and as such be consistent, about the requirement of having to provide a Content-Type header in requests creating and updating media entities, and as such be no stricter then the HTTP specification itself either.

      Description

      In section 8.1.1 wrt Content-Type header, which MUST be specified on requests and responses with a non-empty request or response body, an exception is specified for bodies representing the media stream of a media entity of stream property, in which case that Content-Type header is optional and SHOULD be present.
      However section 11.4.7, dealing with the creation and updating of these media entities and their associated streams, as well as section 11.4.8 pertaining to the update of stream values, both specify that the Content-Type header MUST be specified.
      Are we implicitly saying that the Content-Type is potentially optional while retrieving the media stream of a media entity or a stream property?

        Attachments

          Activity

            People

            • Assignee:
              hubert.heijkers Hubert Heijkers
              Reporter:
              hubert.heijkers Hubert Heijkers
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: