From a691e044705f12715fcd3310a9832dd5de79bff0 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 27 Aug 2013 22:32:51 +0200 Subject: 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. --- lib/multiif.h | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'lib/multiif.h') diff --git a/lib/multiif.h b/lib/multiif.h index d1b0e2fb3..e61c5c6f2 100644 --- a/lib/multiif.h +++ b/lib/multiif.h @@ -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 -- cgit v1.2.1