Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to connect to dav server when filenames/foldernames have special characters (think ampersand) #8966

Closed
cyberduck opened this issue Aug 4, 2015 · 4 comments
Closed

Unable to connect to dav server when filenames/foldernames have special characters (think ampersand) #8966

cyberduck opened this issue Aug 4, 2015 · 4 comments
Assignees
@dkocher
Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation

Comments

@cyberduck
Copy link
Collaborator

9108599 created the issue

Hi,

I was trying to connect to an apache hosted webdav server and was getting the following error:

Not a valid DAV response

After listing the dav contents using firefox to enumerate the dav url I found that there was a filename with the '&' character in it (literally H&H5678). Firefox was displaying the character correctly, and clicking on it returned the contents of the file.

Cyberduck was unable to list to the folder contents, I suspect becuase GetDirectoryList barfs on the specially encoded xml characters like the ampersand.

When I renamed the file (using the application admin UI) to remove the '&' cyberduck was abe to connect to it.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

The & character must be URI encoded in the response. Please report this bug to the vendor of the server software.

@cyberduck
Copy link
Collaborator Author

9108599 commented

Sorry I should have been clearer on this.
When listen the folder in firefox the file name is displayed as uri envoded (using the character sequence for &). So the file H&H5678 shows up as H%26H5678''''.

This would indicate to me that the server is correctly encoding the characters in it's response, but the dav library being used on the client side somehow not able to understand the encoding/escaping.

Is that not the case?

@cyberduck
Copy link
Collaborator Author

9108599 commented

Please see previous comment about clarity here. i believe the response is url encoded already.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I am not aware that Firefox is capable of reading WebDAV PROPFIND responses. I assume what is displayed in Firefox is a HTML document.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck