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

Listing directory Documents failed. Not a valid DAV response (Multi-section). #9521

cyberduck opened this issue May 8, 2016 · 1 comment


Copy link

@cyberduck cyberduck commented May 8, 2016

afb2fd9 created the issue

Upgraded today to v4.9.3 and ran into trouble communicating with Files (confirmed with Files Pro) (Olive Toast Software) on an iPad.

The sequence of events I describe here are accompanied by a set of four screen shots and a dump of the log window.

After successfully connecting to remote iPad the browser window appeared normal. See step 1.png.

I then attempted to navigate the remote file system by double-clicking on the "Documents" icon and received the response shown in step 2.png. A dialog box containing the message beginning with "Listing directory Documents failed. Not a valid DAV response (Multi-section)."

After "retrying" the dialog box was dismissed yet the browser remained on the same page as seen in step 3.png.

Using the "refresh" icon on the tool bar resulted in a successful move into the /Documents directory yet the directory appeared empty as seen in step 4.png. The /Documents directory was actually NOT empty and contained a number of files and directories.

The log window text at the point of step 4 was captured and placed in the accompanying text file.

Best regards,
Joseph DiVerdi


Copy link
Collaborator Author

@cyberduck cyberduck commented May 8, 2016

@dkocher commented

The server is responding with an invalid XML response not compliant with the WebDAV protocol specification. Please report this issue to the server software vendor Olive Toast Software.


@cyberduck cyberduck closed this May 8, 2016
@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.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant