Uploaded image for project: 'OASIS Open Data Protocol (OData) TC'
  1. OASIS Open Data Protocol (OData) TC
  2. ODATA-869

Explicitly state the location of the Content-ID header in a change set

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: V4.0_ERRATA03
    • Component/s: Protocol
    • Labels:
      None
    • Environment:

      Applied

      Description

      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).

        Attachments

          Activity

            People

            • Assignee:
              handl Ralf Handl
              Reporter:
              matt.borges Matthew Borges
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: