blob: 4279a155ceb54a86cb3c6602727f8b19b2b2ec87 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
|
Feature: webdav-related
Background:
Given using api version "1"
Scenario: Unauthenticated call old dav path
Given using old dav path
When connecting to dav endpoint
Then the HTTP status code should be "401"
And there are no duplicate headers
And The following headers should be set
|WWW-Authenticate|Basic realm="Nextcloud", Bearer realm="Nextcloud"|
Scenario: Unauthenticated call new dav path
Given using new dav path
When connecting to dav endpoint
Then the HTTP status code should be "401"
And there are no duplicate headers
And The following headers should be set
|WWW-Authenticate|Basic realm="Nextcloud", Bearer realm="Nextcloud"|
Scenario: Moving a file
Given using old dav path
And As an "admin"
And user "user0" exists
And As an "user0"
When User "user0" moves file "/welcome.txt" to "/FOLDER/welcome.txt"
Then the HTTP status code should be "201"
And Downloaded content when downloading file "/FOLDER/welcome.txt" with range "bytes=0-6" should be "Welcome"
Scenario: Moving and overwriting a file old way
Given using old dav path
And As an "admin"
And user "user0" exists
And As an "user0"
When User "user0" moves file "/welcome.txt" to "/textfile0.txt"
Then the HTTP status code should be "204"
And Downloaded content when downloading file "/textfile0.txt" with range "bytes=0-6" should be "Welcome"
Scenario: Moving a file to a folder with no permissions
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user1" exists
And As an "user1"
And user "user1" created a folder "/testshare"
And as "user1" creating a share with
| path | testshare |
| shareType | 0 |
| permissions | 1 |
| shareWith | user0 |
And As an "user0"
And User "user0" moves file "/textfile0.txt" to "/testshare/textfile0.txt"
And the HTTP status code should be "403"
When Downloading file "/testshare/textfile0.txt"
Then the HTTP status code should be "404"
Scenario: Moving a file to overwrite a file in a folder with no permissions
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user1" exists
And As an "user1"
And user "user1" created a folder "/testshare"
And as "user1" creating a share with
| path | testshare |
| shareType | 0 |
| permissions | 1 |
| shareWith | user0 |
And User "user1" copies file "/welcome.txt" to "/testshare/overwritethis.txt"
And As an "user0"
When User "user0" moves file "/textfile0.txt" to "/testshare/overwritethis.txt"
Then the HTTP status code should be "403"
And Downloaded content when downloading file "/testshare/overwritethis.txt" with range "bytes=0-6" should be "Welcome"
Scenario: Copying a file
Given using old dav path
And As an "admin"
And user "user0" exists
And As an "user0"
When User "user0" copies file "/welcome.txt" to "/FOLDER/welcome.txt"
Then the HTTP status code should be "201"
And Downloaded content when downloading file "/FOLDER/welcome.txt" with range "bytes=0-6" should be "Welcome"
Scenario: Copying and overwriting a file
Given using old dav path
And As an "admin"
And user "user0" exists
And As an "user0"
When User "user0" copies file "/welcome.txt" to "/textfile1.txt"
Then the HTTP status code should be "204"
And Downloaded content when downloading file "/textfile1.txt" with range "bytes=0-6" should be "Welcome"
Scenario: Copying a file to a folder with no permissions
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user1" exists
And As an "user1"
And user "user1" created a folder "/testshare"
And as "user1" creating a share with
| path | testshare |
| shareType | 0 |
| permissions | 1 |
| shareWith | user0 |
And As an "user0"
When User "user0" copies file "/textfile0.txt" to "/testshare/textfile0.txt"
Then the HTTP status code should be "403"
And Downloading file "/testshare/textfile0.txt"
And the HTTP status code should be "404"
Scenario: Copying a file to overwrite a file into a folder with no permissions
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user1" exists
And As an "user1"
And user "user1" created a folder "/testshare"
And as "user1" creating a share with
| path | testshare |
| shareType | 0 |
| permissions | 1 |
| shareWith | user0 |
And User "user1" copies file "/welcome.txt" to "/testshare/overwritethis.txt"
And As an "user0"
When User "user0" copies file "/textfile0.txt" to "/testshare/overwritethis.txt"
Then the HTTP status code should be "403"
And Downloaded content when downloading file "/testshare/overwritethis.txt" with range "bytes=0-6" should be "Welcome"
Scenario: download a file with range
Given using old dav path
And As an "admin"
When Downloading file "/welcome.txt" with range "bytes=52-78"
Then Downloaded content should be "example file for developers"
Scenario: Upload forbidden if quota is 0
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user0" has a quota of "0"
When User "user0" uploads file "data/textfile.txt" to "/asdf.txt"
Then the HTTP status code should be "507"
Scenario: Retrieving folder quota when no quota is set
Given using old dav path
And As an "admin"
And user "user0" exists
When user "user0" has unlimited quota
Then as "user0" gets properties of folder "/" with
|{DAV:}quota-available-bytes|
And the single response should contain a property "{DAV:}quota-available-bytes" with value "-3"
Scenario: Retrieving folder quota when quota is set
Given using old dav path
And As an "admin"
And user "user0" exists
When user "user0" has a quota of "10 MB"
Then as "user0" gets properties of folder "/" with
|{DAV:}quota-available-bytes|
And the single response should contain a property "{DAV:}quota-available-bytes" with value "10485421"
Scenario: Retrieving folder quota of shared folder with quota when no quota is set for recipient
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user1" exists
And user "user0" has unlimited quota
And user "user1" has a quota of "10 MB"
And As an "user1"
And user "user1" created a folder "/testquota"
And as "user1" creating a share with
| path | testquota |
| shareType | 0 |
| permissions | 31 |
| shareWith | user0 |
Then as "user0" gets properties of folder "/testquota" with
|{DAV:}quota-available-bytes|
And the single response should contain a property "{DAV:}quota-available-bytes" with value "10485421"
Scenario: Uploading a file as recipient using webdav having quota
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user1" exists
And user "user0" has a quota of "10 MB"
And user "user1" has a quota of "10 MB"
And As an "user1"
And user "user1" created a folder "/testquota"
And as "user1" creating a share with
| path | testquota |
| shareType | 0 |
| permissions | 31 |
| shareWith | user0 |
And As an "user0"
When User "user0" uploads file "data/textfile.txt" to "/testquota/asdf.txt"
Then the HTTP status code should be "201"
Scenario: Retrieving folder quota when quota is set and a file was uploaded
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user0" has a quota of "1 KB"
And user "user0" adds a file of 93 bytes to "/prueba.txt"
When as "user0" gets properties of folder "/" with
|{DAV:}quota-available-bytes|
Then the single response should contain a property "{DAV:}quota-available-bytes" with value "592"
Scenario: Retrieving folder quota when quota is set and a file was recieved
Given using old dav path
And As an "admin"
And user "user0" exists
And user "user1" exists
And user "user1" has a quota of "1 KB"
And user "user0" adds a file of 93 bytes to "/user0.txt"
And file "user0.txt" of user "user0" is shared with user "user1"
When as "user1" gets properties of folder "/" with
|{DAV:}quota-available-bytes|
Then the single response should contain a property "{DAV:}quota-available-bytes" with value "685"
Scenario: download a public shared file with range
Given user "user0" exists
And As an "user0"
When creating a share with
| path | welcome.txt |
| shareType | 3 |
And Downloading last public shared file with range "bytes=52-78"
Then Downloaded content should be "example file for developers"
Scenario: download a public shared file inside a folder with range
Given user "user0" exists
And As an "user0"
When creating a share with
| path | PARENT |
| shareType | 3 |
And Downloading last public shared file inside a folder "/parent.txt" with range "bytes=1-8"
Then Downloaded content should be "extcloud"
Scenario: Downloading a file on the old endpoint should serve security headers
Given using old dav path
And As an "admin"
When Downloading file "/welcome.txt"
Then The following headers should be set
|Content-Disposition|attachment; filename*=UTF-8''welcome.txt; filename="welcome.txt"|
|Content-Security-Policy|default-src 'none';|
|X-Content-Type-Options |nosniff|
|X-Download-Options|noopen|
|X-Frame-Options|SAMEORIGIN|
|X-Permitted-Cross-Domain-Policies|none|
|X-Robots-Tag|none|
|X-XSS-Protection|1; mode=block|
And Downloaded content should start with "Welcome to your Nextcloud account!"
Scenario: Doing a GET with a web login should work without CSRF token on the old backend
Given Logging in using web as "admin"
When Sending a "GET" to "/remote.php/webdav/welcome.txt" without requesttoken
Then Downloaded content should start with "Welcome to your Nextcloud account!"
Then the HTTP status code should be "200"
Scenario: Doing a GET with a web login should work with CSRF token on the old backend
Given Logging in using web as "admin"
When Sending a "GET" to "/remote.php/webdav/welcome.txt" with requesttoken
Then Downloaded content should start with "Welcome to your Nextcloud account!"
Then the HTTP status code should be "200"
Scenario: Doing a PROPFIND with a web login should not work without CSRF token on the old backend
Given Logging in using web as "admin"
When Sending a "PROPFIND" to "/remote.php/webdav/welcome.txt" without requesttoken
Then the HTTP status code should be "401"
Scenario: Doing a PROPFIND with a web login should work with CSRF token on the old backend
Given Logging in using web as "admin"
When Sending a "PROPFIND" to "/remote.php/webdav/welcome.txt" with requesttoken
Then the HTTP status code should be "207"
Scenario: Upload chunked file asc
Given user "user0" exists
And user "user0" uploads chunk file "1" of "3" with "AAAAA" to "/myChunkedFile.txt"
And user "user0" uploads chunk file "2" of "3" with "BBBBB" to "/myChunkedFile.txt"
And user "user0" uploads chunk file "3" of "3" with "CCCCC" to "/myChunkedFile.txt"
When As an "user0"
And Downloading file "/myChunkedFile.txt"
Then Downloaded content should be "AAAAABBBBBCCCCC"
Scenario: Upload chunked file desc
Given user "user0" exists
And user "user0" uploads chunk file "3" of "3" with "CCCCC" to "/myChunkedFile.txt"
And user "user0" uploads chunk file "2" of "3" with "BBBBB" to "/myChunkedFile.txt"
And user "user0" uploads chunk file "1" of "3" with "AAAAA" to "/myChunkedFile.txt"
When As an "user0"
And Downloading file "/myChunkedFile.txt"
Then Downloaded content should be "AAAAABBBBBCCCCC"
Scenario: Upload chunked file random
Given user "user0" exists
And user "user0" uploads chunk file "2" of "3" with "BBBBB" to "/myChunkedFile.txt"
And user "user0" uploads chunk file "3" of "3" with "CCCCC" to "/myChunkedFile.txt"
And user "user0" uploads chunk file "1" of "3" with "AAAAA" to "/myChunkedFile.txt"
When As an "user0"
And Downloading file "/myChunkedFile.txt"
Then Downloaded content should be "AAAAABBBBBCCCCC"
Scenario: A file that is not shared does not have a share-types property
Given user "user0" exists
And user "user0" created a folder "/test"
When as "user0" gets properties of folder "/test" with
|{http://owncloud.org/ns}share-types|
Then the response should contain an empty property "{http://owncloud.org/ns}share-types"
Scenario: A file that is shared to a user has a share-types property
Given user "user0" exists
And user "user1" exists
And user "user0" created a folder "/test"
And as "user0" creating a share with
| path | test |
| shareType | 0 |
| permissions | 31 |
| shareWith | user1 |
When as "user0" gets properties of folder "/test" with
|{http://owncloud.org/ns}share-types|
Then the response should contain a share-types property with
| 0 |
Scenario: A file that is shared to a group has a share-types property
Given user "user0" exists
And group "group1" exists
And user "user0" created a folder "/test"
And as "user0" creating a share with
| path | test |
| shareType | 1 |
| permissions | 31 |
| shareWith | group1 |
When as "user0" gets properties of folder "/test" with
|{http://owncloud.org/ns}share-types|
Then the response should contain a share-types property with
| 1 |
Scenario: A file that is shared by link has a share-types property
Given user "user0" exists
And user "user0" created a folder "/test"
And as "user0" creating a share with
| path | test |
| shareType | 3 |
| permissions | 31 |
When as "user0" gets properties of folder "/test" with
|{http://owncloud.org/ns}share-types|
Then the response should contain a share-types property with
| 3 |
Scenario: A file that is shared by user,group and link has a share-types property
Given user "user0" exists
And user "user1" exists
And group "group2" exists
And user "user0" created a folder "/test"
And as "user0" creating a share with
| path | test |
| shareType | 0 |
| permissions | 31 |
| shareWith | user1 |
And as "user0" creating a share with
| path | test |
| shareType | 1 |
| permissions | 31 |
| shareWith | group2 |
And as "user0" creating a share with
| path | test |
| shareType | 3 |
| permissions | 31 |
When as "user0" gets properties of folder "/test" with
|{http://owncloud.org/ns}share-types|
Then the response should contain a share-types property with
| 0 |
| 1 |
| 3 |
Scenario: Upload chunked file asc with new chunking
Given using new dav path
And user "user0" exists
And user "user0" creates a new chunking upload with id "chunking-42"
And user "user0" uploads new chunk file "1" with "AAAAA" to id "chunking-42"
And user "user0" uploads new chunk file "2" with "BBBBB" to id "chunking-42"
And user "user0" uploads new chunk file "3" with "CCCCC" to id "chunking-42"
And user "user0" moves new chunk file with id "chunking-42" to "/myChunkedFile.txt"
When As an "user0"
And Downloading file "/myChunkedFile.txt"
Then Downloaded content should be "AAAAABBBBBCCCCC"
Scenario: Upload chunked file desc with new chunking
Given using new dav path
And user "user0" exists
And user "user0" creates a new chunking upload with id "chunking-42"
And user "user0" uploads new chunk file "3" with "CCCCC" to id "chunking-42"
And user "user0" uploads new chunk file "2" with "BBBBB" to id "chunking-42"
And user "user0" uploads new chunk file "1" with "AAAAA" to id "chunking-42"
And user "user0" moves new chunk file with id "chunking-42" to "/myChunkedFile.txt"
When As an "user0"
And Downloading file "/myChunkedFile.txt"
Then Downloaded content should be "AAAAABBBBBCCCCC"
Scenario: Upload chunked file random with new chunking
Given using new dav path
And user "user0" exists
And user "user0" creates a new chunking upload with id "chunking-42"
And user "user0" uploads new chunk file "2" with "BBBBB" to id "chunking-42"
And user "user0" uploads new chunk file "3" with "CCCCC" to id "chunking-42"
And user "user0" uploads new chunk file "1" with "AAAAA" to id "chunking-42"
And user "user0" moves new chunk file with id "chunking-42" to "/myChunkedFile.txt"
When As an "user0"
And Downloading file "/myChunkedFile.txt"
Then Downloaded content should be "AAAAABBBBBCCCCC"
Scenario: A disabled user cannot use webdav
Given user "userToBeDisabled" exists
And As an "admin"
And assure user "userToBeDisabled" is disabled
When Downloading file "/welcome.txt" as "userToBeDisabled"
Then the HTTP status code should be "503"
Scenario: Copying files into a folder with edit permissions
Given using dav path "remote.php/webdav"
And user "user0" exists
And user "user1" exists
And As an "user1"
And user "user1" created a folder "/testcopypermissionsAllowed"
And as "user1" creating a share with
| path | testcopypermissionsAllowed |
| shareType | 0 |
| permissions | 31 |
| shareWith | user0 |
And User "user0" uploads file with content "copytest" to "/copytest.txt"
When User "user0" copies file "/copytest.txt" to "/testcopypermissionsAllowed/copytest.txt"
Then the HTTP status code should be "201"
Scenario: Copying files into a folder without edit permissions
Given using dav path "remote.php/webdav"
And user "user0" exists
And user "user1" exists
And As an "user1"
And user "user1" created a folder "/testcopypermissionsNotAllowed"
And as "user1" creating a share with
| path | testcopypermissionsNotAllowed |
| shareType | 0 |
| permissions | 1 |
| shareWith | user0 |
And User "user0" uploads file with content "copytest" to "/copytest.txt"
When User "user0" copies file "/copytest.txt" to "/testcopypermissionsNotAllowed/copytest.txt"
Then the HTTP status code should be "403"
Scenario: Uploading a file as recipient with limited permissions
Given using new dav path
And As an "admin"
And user "user0" exists
And user "user1" exists
And user "user0" has a quota of "10 MB"
And user "user1" has a quota of "10 MB"
And As an "user1"
And user "user1" created a folder "/testfolder"
And as "user1" creating a share with
| path | testfolder |
| shareType | 0 |
| permissions | 23 |
| shareWith | user0 |
And As an "user0"
And User "user0" uploads file "data/textfile.txt" to "/testfolder/asdf.txt"
And As an "user1"
When User "user1" deletes file "/testfolder/asdf.txt"
Then the HTTP status code should be "204"
Scenario: Creating a folder
Given using old dav path
And user "user0" exists
And user "user0" created a folder "/test_folder"
When as "user0" gets properties of folder "/test_folder" with
|{DAV:}resourcetype|
Then the single response should contain a property "{DAV:}resourcetype" with value "{DAV:}collection"
Scenario: Creating a folder with special chars
Given using old dav path
And user "user0" exists
And user "user0" created a folder "/test_folder:5"
When as "user0" gets properties of folder "/test_folder:5" with
|{DAV:}resourcetype|
Then the single response should contain a property "{DAV:}resourcetype" with value "{DAV:}collection"
Scenario: Removing everything of a folder
Given using old dav path
And As an "admin"
And user "user0" exists
And As an "user0"
And User "user0" moves file "/welcome.txt" to "/FOLDER/welcome.txt"
And user "user0" created a folder "/FOLDER/SUBFOLDER"
And User "user0" copies file "/textfile0.txt" to "/FOLDER/SUBFOLDER/testfile0.txt"
When User "user0" deletes everything from folder "/FOLDER/"
Then user "user0" should see following elements
| /FOLDER/ |
| /PARENT/ |
| /PARENT/parent.txt |
| /textfile0.txt |
| /textfile1.txt |
| /textfile2.txt |
| /textfile3.txt |
| /textfile4.txt |
Scenario: Removing everything of a folder using new dav path
Given using new dav path
And As an "admin"
And user "user0" exists
And As an "user0"
And User "user0" moves file "/welcome.txt" to "/FOLDER/welcome.txt"
And user "user0" created a folder "/FOLDER/SUBFOLDER"
And User "user0" copies file "/textfile0.txt" to "/FOLDER/SUBFOLDER/testfile0.txt"
When User "user0" deletes everything from folder "/FOLDER/"
Then user "user0" should see following elements
| /FOLDER/ |
| /PARENT/ |
| /PARENT/parent.txt |
| /textfile0.txt |
| /textfile1.txt |
| /textfile2.txt |
| /textfile3.txt |
| /textfile4.txt |
Scenario: Checking file id after a move using new endpoint
Given using new dav path
And user "user0" exists
And User "user0" stores id of file "/textfile0.txt"
When User "user0" moves file "/textfile0.txt" to "/FOLDER/textfile0.txt"
Then User "user0" checks id of file "/FOLDER/textfile0.txt"
Scenario: Checking file id after a move overwrite using new chunking endpoint
Given using new dav path
And user "user0" exists
And User "user0" copies file "/textfile0.txt" to "/existingFile.txt"
And User "user0" stores id of file "/existingFile.txt"
And user "user0" creates a new chunking upload with id "chunking-42"
And user "user0" uploads new chunk file "1" with "AAAAA" to id "chunking-42"
And user "user0" uploads new chunk file "2" with "BBBBB" to id "chunking-42"
And user "user0" uploads new chunk file "3" with "CCCCC" to id "chunking-42"
When user "user0" moves new chunk file with id "chunking-42" to "/existingFile.txt"
Then User "user0" checks id of file "/existingFile.txt"
Scenario: Renaming a folder to 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 "/%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 "/%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%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 "/%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 "/%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%5Chola"
Then the HTTP status code should be "400"
|