Bring back proper DAV support #5409
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
4ce72b7 to
e8a3504
Compare
e8a3504 to
2854c61
Compare
Closed
63eee1e to
e375302
Compare
91a0776 to
c25d023
Compare
7920319 to
6dc7b40
Compare
diocas
approved these changes
Nov 28, 2025
Contributor
diocas
left a comment
There was a problem hiding this comment.
No remarks, just happiness
glpatcern
requested changes
Nov 28, 2025
Member
glpatcern
left a comment
There was a problem hiding this comment.
I share the happiness ;-) but we have to see what happens with the OCM logic
6dc7b40 to
fc1e3c8
Compare
glpatcern
approved these changes
Nov 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spaces broke proper DAV support, because returned
hrefs in thePROPFINDalways contained space IDs, even if these were not present in the incoming request. This is fixed now, by writing the href based in the incoming URL