Support for PROPFIND with empty request body #63
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
dabidski
added a commit
to dabidski/dav4rack
that referenced
this pull request
Nov 29, 2020
…PFIND with empty request body.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As http://www.ics.uci.edu/~ejw/authoring/protocol/rfc2518.html#METHOD_PROPFIND suggests: "An empty PROPFIND request body MUST be treated as a request for the names and values of all properties."
I saw that Microsoft's Mini-Redirector used to request PROPFIND with empty request body and after applied this patch it worked fine.
I guess we should have some test for that, how can we make it?