3
3
changelog of the current development status, as one or more of these problems
4
4
may have been fixed since this was written!
6
34. The SOCKS connection codes don't properly acknowledge (connect) timeouts.
6
41. When doing an operation over FTP that requires the ACCT command (but not
7
when logging in), the operation will fail since libcurl doesn't detect this
8
and thus fails to issue the correct command:
9
http://curl.haxx.se/bug/view.cgi?id=1693337
11
40. Mac OS X test failures (Daniel Johnson)
12
http://curl.haxx.se/mail/lib-2007-03/0095.html
14
39. Steffen Rumler's Race Condition in Curl_proxyCONNECT:
15
http://curl.haxx.se/mail/lib-2007-01/0045.html
17
38. Kumar Swamy Bhatt's problem in ftp/ssl "LIST" operation:
18
http://curl.haxx.se/mail/lib-2007-01/0103.html
20
37. Having more than one connection to the same host when doing NTLM
21
authentication (with performs multiple "passes" and authenticates a
22
connection rather than a HTTP request), and particularly when using the
23
multi interface, there's a risk that libcurl will re-use a wrong connection
24
when doing the different passes in the NTLM negotiation and thus fail to
25
negotiate (in seemingly mysterious ways).
27
35. Both SOCKS5 and SOCKS4 proxy connections are done blocking, which is very
28
bad when used with the multi interface.
30
34. The SOCKS4 connection codes don't properly acknowledge (connect) timeouts.
31
Also see #12. According to bug #1556528, even the SOCKS5 connect code does
32
not do it right: http://curl.haxx.se/bug/view.cgi?id=1556528,
8
34
33. Doing multi-pass HTTP authentication on a non-default port does not work.
9
35
This happens because the multi-pass code abuses the redirect following code
39
65
"system context" will make it use wrong(?) user name - at least when compared
40
66
to what winhttp does. See http://curl.haxx.se/bug/view.cgi?id=1281867
42
25. When doing a CONNECT request with curl it doesn't properly handle if the
43
proxy closes the connection within the authentication "negotiation phase".
44
Like if you do HTTPS or similar over a proxy and you use perhaps
45
--proxy-anyauth. There's work in progress on this problem, and a recent
46
patch was posted here: http://curl.haxx.se/mail/lib-2005-08/0074.html
68
23. SOCKS-related problems:
69
A) libcurl doesn't support SOCKS for IPv6.
70
B) libcurl doesn't support FTPS over a SOCKS proxy.
71
C) We don't have any test cases for SOCKS proxy.
72
E) libcurl doesn't support active FTP over a SOCKS proxy
48
23. We don't support SOCKS for IPv6. We don't support FTPS over a SOCKS proxy.
49
We don't have any test cases for SOCKS proxy. We probably have even more
50
bugs and lack of features when a SOCKS proxy is used. And there seem to be a
51
problem with SOCKS when doing FTP: See
52
http://curl.haxx.se/bug/view.cgi?id=1371540
74
We probably have even more bugs and lack of features when a SOCKS proxy is
54
77
22. Sending files to a FTP server using curl on VMS, might lead to curl
55
78
complaining on "unaligned file size" on completion. The problem is related
69
92
Since 7.15.4 at least line endings are converted.
71
19. FTP 3rd party transfers with the multi interface doesn't work. Test:
72
define CURL_MULTIEASY, rebuild curl, run test case 230 - 232.
74
94
16. FTP URLs passed to curl may contain NUL (0x00) in the RFC 1738 <user>,
75
95
<password>, and <fpath> components, encoded as "%00". The problem is that
76
96
curl_unescape does not detect this, but instead returns a shortened C
93
113
12. When connecting to a SOCKS proxy, the (connect) timeout is not properly
94
114
acknowledged after the actual TCP connect (during the SOCKS "negotiate"
95
phase). Pointed out by Lucas. Fix: need to select() and timeout properly.
97
11. Using configure --disable-[protocol] may cause 'make test' to fail for
98
tests using the disabled protocol(s).
100
117
10. To get HTTP Negotiate authentication to work fine, you need to provide a
101
118
(fake) user name (this concerns both curl and the lib) because the code
added
removed
docs/KNOWN_BUGS
