[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-766) 8.2.4 and 8.2.5 should refer to RFC7232 (public comment c201501e00001)
[ https://issues.oasis-open.org/browse/ODATA-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59548#comment-59548 ]
Martin Zurmuehl commented on ODATA-766:
---------------------------------------
Also cleaned up 11.6. asynchronous requests:
The Content-Transfer-Encoding header is not necessary for content-type application/http, because messages enclosed by this type are in "binary" format, see https://tools.ietf.org/html/rfc7230#section-8.3.2; its use is discouraged by RFC 7231, see https://tools.ietf.org/html/rfc7231#appendix-A.5
> 8.2.4 and 8.2.5 should refer to RFC7232 (public comment c201501e00001)
> ----------------------------------------------------------------------
>
> Key: ODATA-766
> URL: https://issues.oasis-open.org/browse/ODATA-766
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: OData Protocol
> Affects Versions: V4.0_ERRATA02
> Environment: [Applied]
> Reporter: Ralf Handl
> Assignee: Martin Zurmuehl
> Priority: Minor
> Fix For: V4.0_ERRATA03
>
>
> Public comment [c201501e00001] (https://lists.oasis-open.org/archives/odata-comment/201501/msg00001.html) points out an incorrect reference to RFC7230 that needs to be replaced with a reference to RFC7232
--
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]