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

HTTP header (content-type) based mime-type detection fails on Mac OS X #6433

Closed
cyberduck opened this issue Dec 10, 2011 · 8 comments
Closed
Assignees
Labels
bug fixed webdav WebDAV Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

34092a6 created the issue

We use Gallery 2.3.1 as a codebase for our hosting service at https://pixi.me/ - we've recently enabled the use of the built-in WebDav feature (doesn't require Apache's mod_dav) to allow our users to upload/download files on the fly.

Unfortunately, using Cyberduck 4.2 on OS X Lion and Microsoft Windows 7 - the WebDAV HTTP header (content-type) based mime-type detection fails. Gallery 2 depends on the content-type header to determine the mime-type of the file.

With this failure, thumbnails will not be generated, ZIP files won't be extracted, etc.. Using cURL works (OS X, FreeBSD, etc..) just fine, and so does Transmit. BitKenix works also (Windows).

I would like to recommend Cyberduck (I use it myself) to our user base, but this issue is just getting in the way.

Please advise, thank you. If you need a test site, let me know.

Best regards,

Steve Caturan

References:

http://gallery.menalto.com/node/61199?page=1
http://thread.gmane.org/gmane.comp.web.gallery.devel/3817

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you please post the transcript from the log drawer (⌘-L) of the Transfers window.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I can replicate this issue. A generic content type of application/octet-stream is sent.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Fixed in sardine-321.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In a4039b7.

@cyberduck
Copy link
Collaborator Author

34092a6 commented

hi David,

I'm still ending up with 0 byte files even after upgrading to 4.2.1 - Just in case you have time, here's a test site : https://pixi.me/gallery2/w/webdav/

webdav is username & password

Please advise, thank you.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:5 wwwpixime]:

hi David,

I'm still ending up with 0 byte files even after upgrading to 4.2.1 - Just in case you have time, here's a test site : https://pixi.me/gallery2/w/webdav/

webdav is username & password

Please advise, thank you.

I suppose this is another issue then.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:6 dkocher]:

Replying to [comment:5 wwwpixime]:

hi David,

I'm still ending up with 0 byte files even after upgrading to 4.2.1 - Just in case you have time, here's a test site : https://pixi.me/gallery2/w/webdav/

webdav is username & password

Please advise, thank you.

I suppose this is another issue then.

There are several issues with this site:

  • As a minor issue it is sending an empty authentication realm.
  • Expect-Continue HTTP handshake is not supported. This does not allow the upload to abort on authentication failures before the payload is sent.

@cyberduck
Copy link
Collaborator Author

34092a6 commented

hi David,

Gallery2 isn't in active development anymore, unfortunately, so we can't file a bug report to resolve the problem.

Is there any way for Cyberduck to compensate for this since most of the other WebDAV clients we tested works fine out of the box, even the mobile apps for IOS/Android.

Please advise, 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.
Labels
bug fixed webdav WebDAV Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants