[Cyberduck-trac] [Cyberduck] #6767: Interoperability with nginx

[Cyberduck]

#6767: Interoperability with nginx
------------------------+---------------------------
 Reporter:  nelson      |         Owner:  dkocher
     Type:  defect      |        Status:  closed
 Priority:  normal      |     Milestone:  4.2.2
Component:  webdav      |       Version:  4.2.1
 Severity:  normal      |    Resolution:  worksforme
 Keywords:  webdav ssl  |  Architecture:  Intel
 Platform:  Windows XP  |
------------------------+---------------------------

Comment (by dkocher):

 Replying to [comment:10 nelson]:
 > Replying to [comment:9 dkocher]:
 > > Replying to [comment:8 nelson]:
 > > >
 > >
 > >
 > > I get a `Broken pipe.` error which suggests the server is closing the
 underlying network connection without responding.
 >
 > Yes, that was a segmentation fault in nginx, see
 http://trac.nginx.org/nginx/ticket/311#comment:1
 >
 > The segfault is fixed in nginx-1.2.6+ and the dav upload problem real
 fix in nginx-1.3.9+
 >
 > Anyway, as distros are only packaging stable nginx versions 1.2.x and
 the dav upload erratic problem is fixed in 1.3.9, can I ask if cyberduck
 can provide an option to disable sending the Expect: 100-continue header ?
 this way nginx stable versions 1.2.x could be used as reliable dav servers
 becuase handling the Expect: header was causing the issue.
 >
 > Basically an option to make  {{{ServicePointManager.Expect100Continue =
 false;}}} see these posts for more info:
 >
 > http://haacked.com/archive/2004/05/15/http-web-request-
 expect-100-continue.aspx
 >
 > http://alihamdar.com/2010/06/19/expect-100-continue/
 >
 > http://msdn.microsoft.com/en-
 us/library/system.net.servicepoint.expect100continue.aspx

 You can use the hidden option


 {{{
 defaults write ch.sudo.cyberduck webdav.expect-continue false
 }}}

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