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

Header Content-Transfer-Encoding not used in HTTP

    XMLWordPrintable

    Details

    • Type: Improvement
    • 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:
      Hide

      In Errata, specify that:
      1) Services should not rely on the header being there in batch requests because it is expected to be made optional in V4.01.
      2) Client should not rely on the header being there in the async/batch response fosr the same reason.

      In V4.01, remove Header Field Content-Transfer-Encoding with value binary

      Show
      In Errata, specify that: 1) Services should not rely on the header being there in batch requests because it is expected to be made optional in V4.01. 2) Client should not rely on the header being there in the async/batch response fosr the same reason. In V4.01, remove Header Field Content-Transfer-Encoding with value binary
    • Resolution:
      Hide

      https://www.oasis-open.org/committees/download.php/57136/odata-v4.0-wd08-part1-protocol-2015-12-15.docx

      Show
      https://www.oasis-open.org/committees/download.php/57136/odata-v4.0-wd08-part1-protocol-2015-12-15.docx

      Description

      In V4 we use the Header Content-Transfer-Encoding:binary together with the Content-Type: application/http in batch payloads (exactly as in V3 ) and in async responses.

      In HTTP 1.1 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.1 and https://tools.ietf.org/html/rfc7230#section-8.3.2) the media type application/http is defined "...Encoding considerations: HTTP messages enclosed by this type are in "binary" format; use of an appropriate Content-Transfer-Encoding is required when transmitted via E-mail."

      And in a section about differences between HTTP and MIME entities, the spec states (http://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.4.5 and https://tools.ietf.org/html/rfc7231#appendix-A.5): "HTTP does not use the Content-Transfer-Encoding (CTE) field of RFC 2045. [...]"

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              martinzurmuehl Martin Zurmuehl
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: