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

Download failure when filename or directory contains # character #9760

Open
cyberduck opened this issue Nov 14, 2016 · 11 comments
Open

Download failure when filename or directory contains # character #9760

cyberduck opened this issue Nov 14, 2016 · 11 comments
Assignees
Labels
bug webdav WebDAV Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Nov 14, 2016

42b76c3 created the issue

Unable to export via WebDAV HTTP/SSL if content contains hashtag (#) - repeated attempts to export/Download files from a server fail if any of the target files contain a hashtag in the filename, sometimes it's just a few files & I can find and change the file name manually then re-try the export/download & it works fine, but other times there may be hundreds of "#" in the collection of filenames, it's too time consuming to find & change them all to re-try the export/download. Both Win7 & Win10 OS on both 32-bit & 64-bit machines.


Attachments

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 14, 2016

@dkocher commented

Please post the transcript from the log drawer of the Transfers window. Choose ⌘-L on Mac or right-click the toolbar from the Transfers window and choose Log on Windows

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 10, 2017

@dkocher commented

I cannot reproduce this issue with Apache/2.2.31 (Amazon) DAV/2.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Jan 11, 2017

@dkocher commented

Milestone renamed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 10, 2017

42b76c3 commented

Still chokes every time one of the exporting files contains a # character in the file name; Win7 & Win10 via WebDAV HTTP/SSL. Not resolved. Version 5.3.7 (23440) I can be exporting 1000 files but if any one of them contains a # in the filename, the whole download will fail.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 5, 2017

@dkocher commented

Ticket retargeted after milestone closed

@cyberduck
Copy link
Collaborator Author

cyberduck commented Feb 11, 2019

42b76c3 commented

Update: it's been a few years now, but still struggling with the same problem when encountering files with a # character in the filename.
Error generated:
"Download FILENAME failed. Unexpected Response (404 Not found). Please contact your web hosting service provider for assistance"
Files that have a # in the filename are not fully downloaded, the name just stops at the # character, omitting the remainder of the path, including the type extension such that the file cannot be opened at all without an associated program extension.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 3, 2019

42b76c3 commented

Will this ever be fixed? I literally instruct all of my users NOT to use the # symbols in their uploaded files or folders even if Microsoft allows it because I can't extract it later with Cyberduck. That's 2k people pissed off at me because they can't use a # symbol to denote a "Change Order # XXXX" or a "Meeting Minutes # XXX" - I even tried to open a support ticket with the software that we use Cyberduck with (e-Builder) and this was their response:

Ginny – I think your true crusade is on the Cyberduck side of the equation. E-Builder enforces the “reserved characters” that Microsoft determines, and # is not on that list. Cyberduck really should be handling that character without problem because it is an acceptable character.

-sigh*

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 31, 2019

@dkocher commented

I cannot reproduce this error with the current snapshot build. Please reopen with server details if still an issue.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Dec 2, 2019

42b76c3 commented

Server details: docs.e-builder.net WebDav , port 443

Account credentials need to be assigned to use this specific application, but really no other application anywhere else in the world of all the people who use Cyberduck globally to move content has issue when there's a "#" symbol in their file/folder names? Syncovery has the same issue with files that have # symbol in them, but Cyberduck is way friendlier/easier in every way to use, we love it aside from this one quirk.

@cyberduck
Copy link
Collaborator Author

cyberduck commented May 14, 2020

42b76c3 commented

So many other companies who use the e-Builder software and rely on Cyberduck for back-end extraction keep hitting this same roadblock with the hashtag ### symbol, ticket has been opened since 2016 - crazy that it's not resolved yet. https://e-builder.ideas.aha.io/ideas/EBE-I-1197. Currently using version 7.3.1

@cyberduck
Copy link
Collaborator Author

cyberduck commented Sep 22, 2021

42b76c3 commented

Still doesn’t work. 5 years now. How can files with ##### in the file name be exported without crashing Cyberduck? Does anyone else have this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug webdav WebDAV Protocol Implementation
Projects
None yet
Development

No branches or pull requests

3 participants