however this is not occurring during connect, but during upload. So it's not Curl_timeleft that is causing our timeout.

The line # where we are getting our "timeout" is 780 in curl_schannel.c
https://github.com/bagder/curl/blob/master/lib/vtls/curl_schannel.c#L780

What happens is the user is uploading a screenshot to AWS S3, and gets about 25-30 seconds in and then there's a slight pause for some network reason and curl gives up (because of that what == 0 check) before the users network becomes uncongested.. (these are unfortunately slow clients).

Right now we are sending out a new beta build that tries to set an explicit timeout of 5 or 10 minutes and seeing if that works around this issue.. If so, then there is definitely something up in L780 in that block that should handle the "no timeout" post-connect case.

---
** [bugs:#1352] WinSSL times out when uploading and timeout option is set to 0**
**Status:** open
**Labels:** winssl 
**Created:** Wed Apr 02, 2014 09:50 PM UTC by Edward Rudd
**Last Updated:** Thu Apr 03, 2014 11:54 AM UTC
**Owner:** Daniel Stenberg
We are using libcurl (currently 7.29) compiled with WinSSL for our Windows build of the application.  We are having a weird issue with where we are receiving a timeout when uploading data and should NOT receive one as we have the CURLOPT_TIMEOUT set to 0 (the default value).   when looking through the code in curl_schannel.c there seems to be a condition not handled while uploading the data.  the Curl_socket_ready method will return 0 (meaning the write socket is not ready), and instead of trying waiting and trying again, the schannel_send method will simply abort with a timeout error. 
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.