[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-869) Explicitly state the location of the Content-ID header in a change set
[ https://issues.oasis-open.org/browse/ODATA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-869: ----------------------------- Assignee: Ralf Handl Environment: Applied (was: Proposed) > Explicitly state the location of the Content-ID header in a change set > ---------------------------------------------------------------------- > > Key: ODATA-869 > URL: https://issues.oasis-open.org/browse/ODATA-869 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData Protocol > Environment: Applied > Reporter: Matthew Borges > Assignee: Ralf Handl > Priority: Minor > Fix For: V4.0_ERRATA03 > > > Although the examples are clear where the Content-ID header should go in a change set, the text is not. The multipart spec (RFC 2045 and 2046), do show that the Content-ID header is a MIME-part-header but it doesn't exclude it from being used in other places (consider the Content-Type header which is used both in the MIME-part-header and part of the OData request). -- 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]