aboutsummaryrefslogtreecommitdiff
path: root/docs/examples/sessioninfo.c
diff options
context:
space:
mode:
authorRemi Gacogne <rgacogne@nuagelabs.fr>2014-02-06 23:16:37 +0100
committerDaniel Stenberg <daniel@haxx.se>2014-02-06 23:21:42 +0100
commit1ebf22cc0eaea3c8513d2bc23937e4388681f3b8 (patch)
tree95553b1f6d103fd566db84dfefb8afb99935d238 /docs/examples/sessioninfo.c
parentff92fcfb907b6aa69bc7e35670797fc0440756bd (diff)
100-continue: fix timeout condition
When using the multi socket interface, libcurl calls the curl_multi_timer_callback asking to be woken up after CURL_TIMEOUT_EXPECT_100 milliseconds. After the timeout has expired, calling curl_multi_socket_action with CURL_SOCKET_TIMEOUT as sockfd leads libcurl to check expired timeouts. When handling the 100-continue one, the following check in Curl_readwrite() fails if exactly CURL_TIMEOUT_EXPECT_100 milliseconds passed since the timeout has been set! It seems logical to consider that having waited for exactly CURL_TIMEOUT_EXPECT_100 ms is enough. Bug: http://curl.haxx.se/bug/view.cgi?id=1334
Diffstat (limited to 'docs/examples/sessioninfo.c')
0 files changed, 0 insertions, 0 deletions