OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-867) Remove header Content-Transfer-Encoding, not used in HTTP


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

Ralf Handl updated ODATA-867:
-----------------------------

    Proposal: Remove mentioning of header field Content-Transfer-Encoding  (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)

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



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]