mbk-lab
/
nextcloud
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix forbidden backslash DAV integration tests

This commit is contained in:
Vincent Petry 2017-03-30 11:31:24 +02:00 committed by Joas Schilling
parent 7b6e4d0dd2
commit d379b197d5
No known key found for this signature in database
GPG Key ID: E166FD8976B3BAC8
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
build/integration/features/webdav-related.feature
View File

@ -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"