Blacklisted filenames like .htaccess & file.parts can be uploaded

[individual-it]

curl 'http://localhost:9140/remote.php/webdav/home/.htaccess' -X PUT -d "mydata" -u user0:123456 -v works without any error

bug or feature?

[butonic]

this is a feature. ocis properly handles .htaccess because there is no php running inside apache that could get be influenced. File uploads are handled with dedicated data services that will make the file available to the storage provider when the upload is done. Atomicity depends on the implementation.

[individual-it]

what about files with .part ?

[PVince81]

in any case we need to have a way to mark those tests that are "skipped on OCIS" as "expected behavior on OCIS".

reopening. let's close the ticket after the test is reenabled/adjusted

[PVince81]

I suspect that depending on the storage implementation, some file names or extensions could be blacklisted, for example when interfacing with another OC 10 instance through OCM.

To me this mean that the storage provider needs to advertise what patterns are accepted and which aren't. Since this is a more complex topic that needs to be discussed at some point, let's keep these tests disabled for now.

[refs]

I suspect that depending on the storage implementation, some file names or extensions could be blacklisted, for example when interfacing with another OC 10 instance through OCM.

To me this mean that the storage provider needs to advertise what patterns are accepted and which aren't. Since this is a more complex topic that needs to be discussed at some point, let's keep these tests disabled for now.

cc @butonic @micbar this seems like a real concern to keep an eye on. Will move it to its own issue so it doesn't get lost in the context of this one.