multi_socket: improved 100-continue timeout handling
When waiting for a 100-continue response from the server, the Curl_readwrite() will refuse to run if called until the timeout has been reached. We timeout code in multi_socket() allows code to run slightly before the actual timeout time, so for test 154 it could lead to the function being executed but refused in Curl_readwrite() and then the application would just sit idling forever. This was detected with runtests.pl -e on test 154.
This commit is contained in:
@@ -22,7 +22,13 @@
|
||||
*
|
||||
***************************************************************************/
|
||||
|
||||
|
||||
/* See multi_socket() for the explanation of this constant. Counted in number
|
||||
of microseconds. */
|
||||
#ifdef WIN32
|
||||
#define MULTI_TIMEOUT_INACCURACY 40000
|
||||
#else
|
||||
#define MULTI_TIMEOUT_INACCURACY 3000
|
||||
#endif
|
||||
|
||||
/*
|
||||
* Prototypes for library-wide functions provided by multi.c
|
||||
|
Reference in New Issue
Block a user