Change sets: do not require the same content type for all request in a change set

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • V4.01_CSD02
    • Affects Version/s: V4.01_CSD01
    • Component/s: Protocol
    • None
    • Environment:

      Applied

      The section on Change Sets currently states:

      Each body part representing an operation in the change set MUST include the same Content-Type header value.

      This does not work for creating media resources and modifying the auto-created media entity, or for creating an entity and then updating its stream properties.

            Assignee:
            Unassigned
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: