Content-Id MUST be unique within Changeset, not within batch

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major
    • V4.01_WD01
    • Affects Version/s: V4.0_CSD03
    • Component/s: Protocol
    • None
    • Hide

      Close with no action

      Show
      Close with no action

      According to section 11.7.3, Changesets in [Protocol]:
      " In addition each request within a change set MUST specify a Content-ID header with a value unique within the batch request"

      "batch request" in this sentence is actually an editorial mistake; each changeset is atomic, and the content-id unique within the scope of the changeset.

            Assignee:
            Unassigned
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: