Scenario Outline: send last chunk twice                                                                                   # /woodpecker/src/github.com/opencloud-eu/opencloud/tests/acceptance/features/coreApiWebdavUploadTUS/lowLevelUpload.feature:45
    Given using <dav-path-version> DAV path                                                                                 # FeatureContext::usingOldOrNewOrSpacesDavPath()
    And user "Alice" has created a new TUS resource on the WebDAV API with these headers:                                   # TUSContext::userHasCreatedNewTUSResourceWithHeaders()
      | Upload-Length   | 10                    |
      | Upload-Metadata | filename ZmlsZS50eHQ= |
    When user "Alice" sends a chunk to the last created TUS Location with offset "0" and data "123" using the WebDAV API    # TUSContext::userSendsAChunkToTUSLocationWithOffsetAndData()
    And user "Alice" sends a chunk to the last created TUS Location with offset "3" and data "4567890" using the WebDAV API # TUSContext::userSendsAChunkToTUSLocationWithOffsetAndData()
    And user "Alice" sends a chunk to the last created TUS Location with offset "3" and data "0000000" using the WebDAV API # TUSContext::userSendsAChunkToTUSLocationWithOffsetAndData()
    Then the HTTP status code should be "404"                                                                               # FeatureContext::thenTheHTTPStatusCodeShouldBe()
    And the content of file "/file.txt" for user "Alice" should be "1234567890"                                             # FeatureContext::contentOfFileForUserShouldBe()

    Examples:
      | dav-path-version |
      | old              |
      | new              |
      | spaces           |
        Failed step: Then the HTTP status code should be "404"
        HTTP status code 409 is not the expected value 404
        Failed asserting that 409 matches expected '404'.