From: Daniel Stenberg <daniel@haxx.se>
Date: Tue, 12 Sep 2006 06:14:10 +0000 (+0000)
Subject: so it seems SOCKS5 too (still) has problems with connect timeouts
X-Git-Tag: curl-7_16_0~180
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=13a5598dc3db2b0ee8288c1ef4cee353ff588a65;p=thirdparty%2Fcurl.git

so it seems SOCKS5 too (still) has problems with connect timeouts
---

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index d16fdbb5b4..dcf64cde7c 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -7,7 +7,8 @@ may have been fixed since this was written!
   bad when used with the multi interface.
 
 34. The SOCKS4 connection codes don't properly acknowledge (connect) timeouts.
-  Also see #12.
+  Also see #12. According to bug #1556528, even the SOCKS5 connect code does
+  not do it right: http://curl.haxx.se/bug/view.cgi?id=#1556528,
 
 33. Doing multi-pass HTTP authentication on a non-default port does not work.
   This happens because the multi-pass code abuses the redirect following code