[OASIS Issue Tracker] (ODATA-824) Header Content-Transfer-Encoding not used in HTTP

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ODATA-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-824:
-----------------------------

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

  was:
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.1. Clients and services are allowed to continue to include the header, but if included it must have the value binary.

       Proposal: 
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 fosr the same reason.

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

  was:
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.1.
2) Client should not rely on the header being there in the async/batch response fosr the same reason.

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


> Header Content-Transfer-Encoding not used in HTTP
> -------------------------------------------------
>
>                 Key: ODATA-824
>                 URL: https://issues.oasis-open.org/browse/ODATA-824
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA02
>            Reporter: Martin Zurmuehl
>              Labels: Clarification
>             Fix For: V4.01_WD01
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)