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

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index d16fdbb5b45ed35e89bd534b1b9cc221e296b770..dcf64cde7c4ced9e3d14ffb796983bb95d4de0a2 100644 (file)
--- 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