aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2020-02-14 16:16:54 +0100
committerDaniel Stenberg <daniel@haxx.se>2020-02-17 00:08:48 +0100
commit4a4b63daaa01ef59b131d91e8e6e6dfe275c0f08 (patch)
tree0d8804b728da55d1296431b1eeb7f446b9e460a5 /docs
parentd60b1b37a1682dee3a53bc6e15b44ecab9811297 (diff)
socks: make the connect phase non-blocking
Removes two entries from KNOWN_BUGS. Closes #4907
Diffstat (limited to 'docs')
-rw-r--r--docs/KNOWN_BUGS17
-rw-r--r--docs/TODO1
2 files changed, 0 insertions, 18 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 60221ff7b..351eca29f 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -87,8 +87,6 @@ problems may have been fixed or changed somewhat since this was written!
9.1 SFTP doesn't do CURLOPT_POSTQUOTE correct
10. SOCKS
- 10.1 SOCKS proxy connections are done blocking
- 10.2 SOCKS don't support timeouts
10.3 FTPS over SOCKS
10.4 active FTP over a SOCKS
@@ -621,21 +619,6 @@ problems may have been fixed or changed somewhat since this was written!
10. SOCKS
-10.1 SOCKS proxy connections are done blocking
-
- Both SOCKS5 and SOCKS4 proxy connections are done blocking, which is very bad
- when used with the multi interface.
-
-10.2 SOCKS don't support timeouts
-
- The SOCKS4 connection codes don't properly acknowledge (connect) timeouts.
- According to bug #1556528, even the SOCKS5 connect code does not do it right:
- https://curl.haxx.se/bug/view.cgi?id=604
-
- When connecting to a SOCK proxy, the (connect) timeout is not properly
- acknowledged after the actual TCP connect (during the SOCKS "negotiate"
- phase).
-
10.3 FTPS over SOCKS
libcurl doesn't support FTPS over a SOCKS proxy.
diff --git a/docs/TODO b/docs/TODO
index 4ed23b456..1d43e7f63 100644
--- a/docs/TODO
+++ b/docs/TODO
@@ -405,7 +405,6 @@
EWOULDBLOCK or similar. Blocking cases include:
- Name resolves on non-windows unless c-ares or the threaded resolver is used
- - SOCKS proxy handshakes
- file:// transfers
- TELNET transfers
- The "DONE" operation (post transfer protocol-specific actions) for the