[Cyberduck-trac] [Cyberduck] #2896: No fallback for Expectation Failure

Cyberduck trac at trac.cyberduck.ch
Sat Nov 20 15:15:43 CET 2010

#2896: No fallback for Expectation Failure
    Reporter:  anonymous                |        Owner:  dkocher 
        Type:  defect                   |       Status:  reopened
    Priority:  normal                   |    Milestone:          
   Component:  webdav                   |      Version:  3.7     
    Severity:  normal                   |   Resolution:          
    Keywords:  webdav expected rfc2616  |     Platform:          
Architecture:                           |  

Comment (by dkocher):

 Replying to [comment:2
 > 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:
 >   Because of the presence of older implementations, the protocol allows
 ambiguous situations in which a client may send "Expect: 100- continue"
 without receiving either a 417 (Expectation Failed) status or a 100
 (Continue) status
 > 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.

 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.

Ticket URL: <http://trac.cyberduck.ch/ticket/2896#comment:5>
Cyberduck <http://cyberduck.ch>
Open source FTP, SFTP, WebDAV, Cloud Files, Google Docs & Amazon S3 Browser for Mac & Windows.

More information about the Cyberduck-trac mailing list