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

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