diff options
| author | Vincent Petry <pvince81@owncloud.com> | 2017-03-30 11:31:24 +0200 |
|---|---|---|
| committer | Joas Schilling <coding@schilljs.com> | 2017-04-26 15:47:59 +0200 |
| commit | d379b197d5968e144e5e4e31661ae1f2cf03e2b6 (patch) | |
| tree | 0eedc6268a31ae9218cf1c4eef572671de3d179b /build/integration | |
| parent | 7b6e4d0dd2dce40fcc7da9de2b7e49b26dfe1914 (diff) | |
| download | nextcloud-server-d379b197d5968e144e5e4e31661ae1f2cf03e2b6.tar.gz nextcloud-server-d379b197d5968e144e5e4e31661ae1f2cf03e2b6.zip | |
Fix forbidden backslash DAV integration tests
Diffstat (limited to 'build/integration')
| -rw-r--r-- | build/integration/features/webdav-related.feature | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/build/integration/features/webdav-related.feature b/build/integration/features/webdav-related.feature index d0eb3fb4bf4..b8ed1c4a778 100644 --- a/build/integration/features/webdav-related.feature +++ b/build/integration/features/webdav-related.feature @@ -541,40 +541,40 @@ Feature: webdav-related Given using old dav path And user "user0" exists And user "user0" created a folder "/testshare" - When User "user0" moves folder "/testshare" to "/%2F" - Then the HTTP status code should be "403" + When User "user0" moves folder "/testshare" to "/%5C" + Then the HTTP status code should be "400" Scenario: Renaming a folder beginning with a backslash encoded should return an error using old endpoint Given using old dav path And user "user0" exists And user "user0" created a folder "/testshare" - When User "user0" moves folder "/testshare" to "/%2Ftestshare" - Then the HTTP status code should be "403" + When User "user0" moves folder "/testshare" to "/%5Ctestshare" + Then the HTTP status code should be "400" Scenario: Renaming a folder including a backslash encoded should return an error using old endpoint Given using old dav path And user "user0" exists And user "user0" created a folder "/testshare" - When User "user0" moves folder "/testshare" to "/hola%2Fhola" - Then the HTTP status code should be "403" + When User "user0" moves folder "/testshare" to "/hola%5Chola" + Then the HTTP status code should be "400" Scenario: Renaming a folder to a backslash encoded should return an error using new endpoint Given using new dav path And user "user0" exists And user "user0" created a folder "/testshare" - When User "user0" moves folder "/testshare" to "/%2F" - Then the HTTP status code should be "403" + When User "user0" moves folder "/testshare" to "/%5C" + Then the HTTP status code should be "400" Scenario: Renaming a folder beginning with a backslash encoded should return an error using new endpoint Given using new dav path And user "user0" exists And user "user0" created a folder "/testshare" - When User "user0" moves folder "/testshare" to "/%2Ftestshare" - Then the HTTP status code should be "403" + When User "user0" moves folder "/testshare" to "/%5Ctestshare" + Then the HTTP status code should be "400" Scenario: Renaming a folder including a backslash encoded should return an error using new endpoint Given using new dav path And user "user0" exists And user "user0" created a folder "/testshare" - When User "user0" moves folder "/testshare" to "/hola%2Fhola" - Then the HTTP status code should be "403" + When User "user0" moves folder "/testshare" to "/hola%5Chola" + Then the HTTP status code should be "400" |