From 13a5598dc3db2b0ee8288c1ef4cee353ff588a65 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 12 Sep 2006 06:14:10 +0000 Subject: so it seems SOCKS5 too (still) has problems with connect timeouts --- docs/KNOWN_BUGS | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index d16fdbb5b..dcf64cde7 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 -- cgit v1.2.3