aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2009-05-11 12:40:48 +0000
committerDaniel Stenberg <daniel@haxx.se>2009-05-11 12:40:48 +0000
commit63270b0665a54ea7305eca505a2a0217cf97455b (patch)
treeeca51f9805f8f380fb9b2638bba1b0f5048d8b8c
parentbcdbba05d39262cfd0fa5c9d3081bb595457edb9 (diff)
Added KNOWN_BUGS #65, and marked it for TODO in the _next_ release as I'm
not in the mood enough to fight this now. 65. When doing FTP over a socks proxy or CONNECT through HTTP proxy and the multi interface is used, libcurl will fail if the (passive) TCP connection for the data transfer isn't more or less instant as the code does not properly wait for the connect to be confirmed. See test case 564 for a first shot at a test case.
-rw-r--r--TODO-RELEASE6
-rw-r--r--docs/KNOWN_BUGS6
2 files changed, 9 insertions, 3 deletions
diff --git a/TODO-RELEASE b/TODO-RELEASE
index 3d2d4bbdf..4f7858aa7 100644
--- a/TODO-RELEASE
+++ b/TODO-RELEASE
@@ -8,9 +8,6 @@ To be addressed in 7.19.5 (planned release: May 2009)
- reviewed
- awaiting patch rework/breakdown
-235 - #2784055, connect race with multi and socks proxy
- Code adjustment for FTP over socks proxy remains
-
236 - timeout in milliseconds doesn't seem to work
http://curl.haxx.se/mail/lib-2009-05/0021.html
@@ -21,3 +18,6 @@ To be addressed in 7.19.6 (planned release: July 2009)
226 - Active Mode FTPS Data Port Range
+235 - KNOWN_BUG #65
+ Code adjustment for FTP over socks proxy remains
+
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 47d256e42..2e3ab82d5 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -3,6 +3,12 @@ join in and help us correct one or more of these! Also be sure to check the
changelog of the current development status, as one or more of these problems
may have been fixed since this was written!
+65. When doing FTP over a socks proxy or CONNECT through HTTP proxy and the
+ multi interface is used, libcurl will fail if the (passive) TCP connection
+ for the data transfer isn't more or less instant as the code does not
+ properly wait for the connect to be confirmed. See test case 564 for a first
+ shot at a test case.
+
64. The threaded resolver used in libcurl on Windows has some kind of race
problem when multiple simultanoes resolves are done, like with the multi
interface transferring many files in parallell: