[Cyberduck-trac] [Cyberduck] #7642: fallback to "Expect: 100-continue" and Chunked Uploads (was: fallback method when a server fails to respond to an "Expect: 100-continue" request and when chunked uploads are not supported by the server.)

Cyberduck trac at trac.cyberduck.io
Wed Nov 27 05:13:10 UTC 2013


#7642: fallback to "Expect: 100-continue" and Chunked Uploads
-----------------------+------------------------------
 Reporter:  wwwpixime  |         Owner:  dkocher
     Type:  defect     |        Status:  new
 Priority:  lowest     |     Milestone:
Component:  webdav     |       Version:  Nightly Build
 Severity:  minor      |    Resolution:
 Keywords:             |  Architecture:
 Platform:             |
-----------------------+------------------------------
Description changed by wwwpixime:

Old description:

> hi David,
>
> When uploading files to https://g2.pixi.me/w/webdav/ - Cyberduck only
> render 0-byte files. Finder's built-in WebDAV client and Forklift 2 does
> the same thing.
>
> I asked  a number of the developers who's WebDAV-apps we tested about
> this issue and was told they use a fallback method when a server fails to
> respond to an "Expect: 100-continue" request and when chunked uploads are
> not supported by the server. The fallback method ensures files are
> properly uploaded, not ending up 0-byte filenames.
>
> If you can shed some light on this, it'd be much appreciated. Even a fix
> is not an option for Cyberduck, at least I can lay this issue to rest.
>
> Thanks very much!

New description:

 hi David,

 When connecting to https://g2.pixi.me/w/webdav/, Cyberduck issues two HEAD
 /w/webdav/ requests both ending up in 500 error and throws an error prompt
 in the UI.  I've only seen the use of HEAD from another IOS app. Most of
 the other ones start with OPTIONS , then PROPFIND

 When uploading files to https://g2.pixi.me/w/webdav/ - Cyberduck only
 render 0-byte files. Finder's built-in WebDAV client and Forklift 2 does
 the same thing.

 I asked  a number of the developers who's WebDAV-apps we tested about this
 issue and was told they use a fallback method when a server fails to
 respond to an "Expect: 100-continue" request and when chunked uploads are
 not supported by the server. The fallback method ensures files are
 properly uploaded, not ending up 0-byte filenames.

 If you can shed some light on this, it'd be much appreciated. Even a fix
 is not an option for Cyberduck, at least I can lay this issue to rest. And
 will make a donation for pushing to support better, more secure TLS
 protocols.

 Thanks very much!

--

-- 
Ticket URL: <https://trac.cyberduck.io/ticket/7642#comment:1>
Cyberduck <http://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows


More information about the Cyberduck-trac mailing list