Header Content-Transfer-Encoding not used in HTTP

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • V4.01_WD01
    • Affects Version/s: V4.0_ERRATA02
    • Component/s: Protocol
    • 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 4.01.
      2) Client should not rely on the header being there in the async/batch response for the same reason.

      In 4.01, remove Header Field Content-Transfer-Encoding with value binary
      make sure that we make the header optional in V4.01 and not forbid it

      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 4.01. 2) Client should not rely on the header being there in the async/batch response for the same reason. In 4.01, remove Header Field Content-Transfer-Encoding with value binary make sure that we make the header optional in V4.01 and not forbid it
    • Hide

      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59028/odata-v4.01-wd01-part1-protocol.docx

      Show
      https://www.oasis-open.org/apps/org/workgroup/odata/download.php/59028/odata-v4.01-wd01-part1-protocol.docx

      In Issue #823, applied to Errata 3 we cautioned clients and services that they should not rely on the Content-Transfer-Encoding header.

      This is to track removal of the required Content-Transfer-Encoding header in 4.01. Clients and services are allowed to continue to include the header, but if included it must have the value binary.

            Assignee:
            Unassigned
            Reporter:
            martinzurmuehl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: