Skip to content

ACID Violation: CHC PUT Deletes Existing Configuration on Invalid Payload #194

@ErikGaida

Description

@ErikGaida
  1. Create PS
  2. Create CHC
    2.1. GET CHC for PS from step 1.
  3. PUT {{m1_url}}/3gpp-m1/v2/provisioning-sessions/{{provisioning_session_id}}/content-hosting-configuration
    body for 3:
{
    "name": "Test CHC Invalid Update",
    "distributionConfigurations": [
        {
            "contentPreparationTemplateURLs": {
                "urlTemplate": "http://example.com/{provisioningSessionId}/manifest.m3u8"
            },
            "entryPoint": {
                "relativePath": "/starts-with-slash-is-invalid",
                "contentType": "application/x-mpegURL"
            }
        }
    ]
}

3.1 see 400 From step 3.
4. do again GET CHC for PS from step 1.
5. See 404 from step 4. the CHC is deleted

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions