[Bug]: Litmus 0.14 not passing depending on WebDAV endpoint
Open
Nobody has claimed this yet.
0. Needs triage
CI
feature: dav
technical debt
tests
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.