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
No fallback for Expectation Failure #2896
Comments
See (http://redmine.lighttpd.net/issues/show/1017). Apparently this is fixed in the 1.5 branch of lighthttpd. |
I strongly disagree with your view here. Older servers, embedded boxes, etc will not be able to upgrade quickly to newer, compliant, http servers. Thus rendering Cyberduck incompatible with any outdated web server. As per the rfc 2616 8.2.3: Cyberduck is awesome, I see no reason if it complies with the above for it not to ignore the 417 lighttpd, or other servers, might return. |
Replying to [comment:2 https://www.google.com/accounts/o8/id?id=aitoawkgh5nrdkuu4brr1gol37zddvisyqhuui0]:
The reason that we require support for continuation is that the user experience for failed uploads is very bad otherwise. All data is transmitted before any error about possible problems is displayed. |
I am using webdav with popular HTTP servers lighttpd and nginx. Latest version of Cyberduck breaks uploading, giving 417 HTTP error.
In fact lighttpd really does not support "Expect:" field. The problem is that there are no fallback (to HTTP/1.0). Switching to HTTP/1.0 after receiving 417 error would be the best solution.
The text was updated successfully, but these errors were encountered: