[Bug]: Litmus 0.14 not passing depending on WebDAV endpoint

provokateurin commented 1 year ago

⚠️ This issue respects the following points: ⚠️

[X] This is a bug, not a question or a configuration/webserver/proxy issue.
[X] This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
[X] Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
[X] I agree to follow Nextcloud's Code of Conduct.

Bug description

We currently only test against litmus 0.13, but https://github.com/notroj/litmus/commit/4a6c2775cc06bd0977779ee53ab9dfbeef8bd5fb introduced a new check which breaks our litmus-v1 but not our litmus-v2 tests. There has to be some inconsistency in the error handling between the used WebDAV endpoints.

Steps to reproduce

Use litmus 0.14
Run make URL="http://localhost/remote.php/webdav" CREDS="admin admin" TESTS="basic" check
Run make URL="http://localhost/remote.php/dav/files/admin" CREDS="admin admin" TESTS="basic" check

Expected behavior

Both test runs should pass, but the second one fails with 5. put_no_parent......... FAIL (PUT with missing intermediate collection gave 404, MUST be 409 [RFC4918:S9.7.1]) while the first one passes that test successfully.

Installation method

None

Nextcloud Server version

27

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

[ ] Default user-backend (database)
[ ] LDAP/ Active Directory
[ ] SSO - SAML
[ ] Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

provokateurin commented 1 year ago

I also found out that the different endpoints expose different webdav capabilities. dav/files/... only exposes access-control while webdav only exposes extended-mkcol, nextcloud-checksum-update. I would expect both endpoints to behave exactly the same, so this seems to be another problem as well? Maybe this issue should be converted in to a general issue about the different possible webdav endpoints and their behavior.

xavierW commented 6 months ago

why the litmus go is so hard to read ,anyone who known that?

provokateurin commented 6 months ago

@xavierW what are you talking about?

xavierW commented 6 months ago

邮件已收到，我会尽快阅读并回复，谢谢

nextcloud / server