Fix prefix-related issues in WebDAV adapter #1533
Merged
Conversation
This file contains 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
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.
Hi,
using the prefix option with the WebDAV adapter currently has multiple issues and works only for simple ascii prefixes in paths that already exist on the destination server.
Basically, all paths are encoded BEFORE adding the prefix. This means that the prefix is never encoded, and a simple space character in the prefix is enough to generate errors for any operation.
The second issue is that the functionality for auto-creating the directories on the server does not add the prefix before iterating over its split components, and so it fails to create the directory tree when the prefix itself does not exist on the server.
Thanks