summaryrefslogtreecommitdiff
path: root/docs/FAQ
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2009-02-23 21:21:00 +0000
committerDaniel Stenberg <daniel@haxx.se>2009-02-23 21:21:00 +0000
commit2afb88e2ce8dc5e1174bd7e79d41274724626dd0 (patch)
tree5fd3abaf61c03c2018a04538691cf1b3747295e1 /docs/FAQ
parent6c9f37d263593bd72759cc2c0d275a3a9cd47b19 (diff)
downloadcurl-2afb88e2ce8dc5e1174bd7e79d41274724626dd0.tar.gz
4.17 Non-functional connect timeouts
Diffstat (limited to 'docs/FAQ')
-rw-r--r--docs/FAQ22
1 files changed, 20 insertions, 2 deletions
diff --git a/docs/FAQ b/docs/FAQ
index 8d4b9f2f1..d2b9988c7 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -1,4 +1,4 @@
-Updated: Jan 14, 2009 (http://curl.haxx.se/docs/faq.html)
+Updated: Feb 23, 2009 (http://curl.haxx.se/docs/faq.html)
_ _ ____ _
___| | | | _ \| |
/ __| | | | |_) | |
@@ -71,6 +71,7 @@ FAQ
4.14 Redirects work in browser but not with curl!
4.15 FTPS doesn't work
4.16 My HTTP POST or PUT requests are slow!
+ 4.17 Non-functional connect timeouts on Windows
5. libcurl Issues
5.1 Is libcurl thread-safe?
@@ -885,6 +886,23 @@ FAQ
You can disable libcurl's use of the Expect: header the same way you disable
any header, using -H / CURLOPT_HTTPHEADER, or by forcing it to use HTTP 1.0.
+ 4.17 Non-functional connect timeouts
+
+ In most Windows setups having a timeout longer than 21 seconds make no
+ difference, as it will only send 3 TCP SYN packets and no more. The second
+ packet sent three seconds after the first and the third six seconds after
+ the second. No more than three packets are sent, no matter how long the
+ timeout is set.
+
+ See option TcpMaxConnectRetransmissions on this page:
+ http://support.microsoft.com/?scid=kb%3Ben-us%3B175523&x=6&y=7
+
+ Also, even on non-Windows systems there may run a firewall or anti-virus
+ software or similar that accepts the connection but does not actually do
+ anything else. This will make (lib)curl to consider the connection connected
+ and thus the connect timeout won't trigger.
+
+
5. libcurl Issues
5.1 Is libcurl thread-safe?
@@ -898,7 +916,7 @@ FAQ
If you use a OpenSSL-powered libcurl in a multi-threaded environment, you
need to provide one or two locking functions:
- http://www.openssl.org/docs/crypto/threads.html#DESCRIPTION
+ http://www.openssl.org/docs/crypto/threads.html
If you use a GnuTLS-powered libcurl in a multi-threaded environment, you
need to provide locking function(s) for libgcrypt (which is used by GnuTLS