Please advise, and thank you for really taking the time to look into this.įramework: Apache/mod_dav (responds to HTTP.EXPECT_DIRECTIVE with 100-Continue) I am seriously desperate to pay for this option because it will benefit so many (of my) users and resolve this particular PUT request issue. When disabled - Cyberduck sends PUT request (without HTTP.EXPECT_DIRECTIVE eliminating 0 byte files altogether. When enabled (default) - Cyberduck sends PUT requests with HTTP.EXPECT_DIRECTIVE
#HANDSHAKER 10.7.5 MAC FULL#
I think the ideal solution lies within "headers.remove(HTTP.EXPECT_DIRECTIVE) " that should be controlled in the UI (Preferences > Transfers > General > Uploads, or under Open Connection > More Options) so the user has full control to disable/enable it whenever needed, on demand.
Thank you for adding a workaround but it's now ending up with duplicate 0-byte files, which can result in 500 Internal Server errors when deleted from within the client itself - I'd have to use a web browser to bypass the errors.
0 kommentar(er)
