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

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

      Applied

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

            Assignee:
            handl
            Reporter:
            matt.borges
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: