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-824) Header Content-Transfer-Encoding not used in HTTP

Michael Pizzo created ODATA-824:

             Summary: 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
         Environment: [Proposed]
            Reporter: Martin Zurmuehl
             Fix For: V4.1_WD01, V4.0_ERRATA03

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

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