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

Bad Request error response for downloads #7902

Closed
cyberduck opened this issue Apr 26, 2014 · 4 comments
Closed

Bad Request error response for downloads #7902

cyberduck opened this issue Apr 26, 2014 · 4 comments
Assignees
@dkocher
Labels
bug high priority thirdparty Issue caused by third party webdav WebDAV Protocol Implementation

Comments

@cyberduck
Copy link
Collaborator

3688b4d created the issue

I am using the SanDisk Connect and using Cyberduck to connect to it and upload/download files (on PC, windows 7 x64bit) and I get an error saying "Cannot Read Files Attributes; Bad Request" when trying to download files wirelessly from my drive. I contacted SanDisk about this issue, and they say they get the same issue while trying to download. (Uploading and all other features i tried work perfectly fine).

Thank you!

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

The server should support a PROPFIND request on a single resource. Please file a bug report with the server vendor SanDisk.

@cyberduck
Copy link
Collaborator Author

6185a8c commented

I am receiving the same problem. Sandisk is putting the blame on cyberduck, cyberduck is putting the blame on sandisk. Can this please be reopened so we can find a solution?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

From RFC 4918

All DAV-compliant resources MUST support the PROPFIND method and the propfind XML element (Section 14.20) along with all XML elements defined for use with that element.

@cyberduck
Copy link
Collaborator Author

d37e216 commented

The drive works with older versions of Cyberduck like 3.3 and 4.0.

Does anyone know at what point Cyberduck changed how it handles connecting to WebDAV servers so that I can use a more recent version than the two listed above? Thanks.

@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 high priority 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