diff options
Diffstat (limited to 'docs/KNOWN_BUGS')
| -rw-r--r-- | docs/KNOWN_BUGS | 138 |
1 files changed, 69 insertions, 69 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 46a02aedc..910db4dd7 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -18,19 +18,19 @@ problems may have been fixed or changed somewhat since this was written! 1.5 Expect-100 meets 417 1.6 Unnecessary close when 401 received waiting for 100 1.7 Deflate error after all content was received - 1.8 DoH isn't used for all name resolves when enabled + 1.8 DoH is not used for all name resolves when enabled 1.11 CURLOPT_SEEKFUNCTION not called with CURLFORM_STREAM 2. TLS 2.1 CURLINFO_SSL_VERIFYRESULT has limited support 2.2 DER in keychain 2.3 Unable to use PKCS12 certificate with Secure Transport - 2.4 Secure Transport won't import PKCS#12 client certificates without a password + 2.4 Secure Transport will not import PKCS#12 client certificates without a password 2.5 Client cert handling with Issuer DN differs between backends 2.6 CURL_GLOBAL_SSL 2.7 Client cert (MTLS) issues with Schannel 2.8 Schannel disable CURLOPT_SSL_VERIFYPEER and verify hostname - 2.9 TLS session cache doesn't work with TFO + 2.9 TLS session cache does not work with TFO 2.10 Store TLS context per transfer instead of per connection 2.11 Schannel TLS 1.2 handshake bug in old Windows versions 2.12 FTPS with Schannel times out file list operation @@ -53,7 +53,7 @@ problems may have been fixed or changed somewhat since this was written! 5.2 curl-config --libs contains private details 5.3 curl compiled on OSX 10.13 failed to run on OSX 10.10 5.4 Build with statically built dependency - 5.5 can't handle Unicode arguments in non-Unicode builds on Windows + 5.5 cannot handle Unicode arguments in non-Unicode builds on Windows 5.7 Visual Studio project gaps 5.8 configure finding libs in wrong directory 5.9 Utilize Requires.private directives in libcurl.pc @@ -66,14 +66,14 @@ problems may have been fixed or changed somewhat since this was written! 6.2 MIT Kerberos for Windows build 6.3 NTLM in system context uses wrong name 6.4 Negotiate and Kerberos V5 need a fake user name - 6.5 NTLM doesn't support password with § character + 6.5 NTLM does not support password with § character 6.6 libcurl can fail to try alternatives with --proxy-any - 6.7 Don't clear digest for single realm + 6.7 Do not clear digest for single realm 6.8 RTSP authentication breaks without redirect support 6.9 SHA-256 digest not supported in Windows SSPI builds 6.10 curl never completes Negotiate over HTTP 6.11 Negotiate on Windows fails - 6.12 Can't use Secure Transport with Crypto Token Kit + 6.12 cannot use Secure Transport with Crypto Token Kit 7. FTP 7.1 FTP without or slow 220 response @@ -89,12 +89,12 @@ problems may have been fixed or changed somewhat since this was written! 7.11 FTPS upload data loss with TLS 1.3 8. TELNET - 8.1 TELNET and time limitations don't work + 8.1 TELNET and time limitations do not work 8.2 Microsoft telnet server 9. SFTP and SCP - 9.1 SFTP doesn't do CURLOPT_POSTQUOTE correct - 9.2 wolfssh: publickey auth doesn't work + 9.1 SFTP does not do CURLOPT_POSTQUOTE correct + 9.2 wolfssh: publickey auth does not work 9.3 Remote recursive folder creation with SFTP 10. SOCKS @@ -104,13 +104,13 @@ problems may have been fixed or changed somewhat since this was written! 11. Internals 11.1 Curl leaks .onion hostnames in DNS 11.2 error buffer not set if connection to multiple addresses fails - 11.3 Disconnects don't do verbose + 11.3 Disconnects do not do verbose 11.4 HTTP test server 'connection-monitor' problems 11.5 Connection information when using TCP Fast Open 11.6 slow connect to localhost on Windows 11.7 signal-based resolver timeouts 11.8 DoH leaks memory after followlocation - 11.9 DoH doesn't inherit all transfer options + 11.9 DoH does not inherit all transfer options 11.10 Blocking socket operations in non-blocking API 11.11 A shared connection cache is not thread-safe 11.12 'no_proxy' string-matches IPv6 numerical addresses @@ -122,7 +122,7 @@ problems may have been fixed or changed somewhat since this was written! 12. LDAP 12.1 OpenLDAP hangs after returning results 12.2 LDAP on Windows does authentication wrong? - 12.3 LDAP on Windows doesn't work + 12.3 LDAP on Windows does not work 12.4 LDAPS with NSS is slow 13. TCP/IP @@ -164,8 +164,8 @@ problems may have been fixed or changed somewhat since this was written! 18.5 HTTP/3 download with quiche halts after a while 18.6 HTTP/3 multipart POST with quiche fails 18.7 HTTP/3 quiche upload large file fails - 18.8 HTTP/3 doesn't support client certs - 18.9 connection migration doesn't work + 18.8 HTTP/3 does not support client certs + 18.9 connection migration does not work ============================================================================== @@ -218,11 +218,11 @@ problems may have been fixed or changed somewhat since this was written! See https://github.com/curl/curl/issues/2719 -1.8 DoH isn't used for all name resolves when enabled +1.8 DoH is not used for all name resolves when enabled Even if DoH is specified to be used, there are some name resolves that are done without it. This should be fixed. When the internal function - `Curl_resolver_wait_resolv()` is called, it doesn't use DoH to complete the + `Curl_resolver_wait_resolv()` is called, it does not use DoH to complete the resolve as it otherwise should. See https://github.com/curl/curl/pull/3857 and @@ -231,11 +231,11 @@ problems may have been fixed or changed somewhat since this was written! 1.11 CURLOPT_SEEKFUNCTION not called with CURLFORM_STREAM I'm using libcurl to POST form data using a FILE* with the CURLFORM_STREAM - option of curl_formadd(). I've noticed that if the connection drops at just + option of curl_formadd(). I have noticed that if the connection drops at just the right time, the POST is reattempted without the data from the file. It - seems like the file stream position isn't getting reset to the beginning of + seems like the file stream position is not getting reset to the beginning of the file. I found the CURLOPT_SEEKFUNCTION option and set that with a - function that performs an fseek() on the FILE*. However, setting that didn't + function that performs an fseek() on the FILE*. However, setting that did not seem to fix the issue or even get called. See https://github.com/curl/curl/issues/768 @@ -249,14 +249,14 @@ problems may have been fixed or changed somewhat since this was written! 2.2 DER in keychain - Curl doesn't recognize certificates in DER format in keychain, but it works + Curl does not recognize certificates in DER format in keychain, but it works with PEM. https://curl.se/bug/view.cgi?id=1065 2.3 Unable to use PKCS12 certificate with Secure Transport See https://github.com/curl/curl/issues/5403 -2.4 Secure Transport won't import PKCS#12 client certificates without a password +2.4 Secure Transport will not import PKCS#12 client certificates without a password libcurl calls SecPKCS12Import with the PKCS#12 client certificate, but that function rejects certificates that do not have a password. @@ -264,7 +264,7 @@ problems may have been fixed or changed somewhat since this was written! 2.5 Client cert handling with Issuer DN differs between backends - When the specified client certificate doesn't match any of the + When the specified client certificate does not match any of the server-specified DNs, the OpenSSL and GnuTLS backends behave differently. The github discussion may contain a solution. @@ -308,7 +308,7 @@ problems may have been fixed or changed somewhat since this was written! https://github.com/curl/curl/issues/3284 -2.9 TLS session cache doesn't work with TFO +2.9 TLS session cache does not work with TFO See https://github.com/curl/curl/issues/4301 @@ -356,7 +356,7 @@ problems may have been fixed or changed somewhat since this was written! handshake, curl has sent an HTTP request to the server and at the same time the server has sent a TLS hello request (renegotiate) to curl. Both are waiting for the other to respond. OpenSSL is supposed to send a handshake - response but doesn't. + response but does not. https://github.com/curl/curl/issues/6785 https://github.com/openssl/openssl/issues/14722 @@ -383,7 +383,7 @@ problems may have been fixed or changed somewhat since this was written! 3.4 AUTH PLAIN for SMTP is not working on all servers - Specifying "--login-options AUTH=PLAIN" on the command line doesn't seem to + Specifying "--login-options AUTH=PLAIN" on the command line does not seem to work correctly. See https://github.com/curl/curl/issues/4080 @@ -392,7 +392,7 @@ problems may have been fixed or changed somewhat since this was written! 4.1 -J and -O with %-encoded file names - -J/--remote-header-name doesn't decode %-encoded file names. RFC6266 details + -J/--remote-header-name does not decode %-encoded file names. RFC6266 details how it should be done. The can of worm is basically that we have no charset handling in curl and ascii >=128 is a challenge for us. Not to mention that decoding also means that we need to check for nastiness that is attempted, @@ -400,10 +400,10 @@ problems may have been fixed or changed somewhat since this was written! embedded slashes should be cut off. https://curl.se/bug/view.cgi?id=1294 - -O also doesn't decode %-encoded names, and while it has even less + -O also does not decode %-encoded names, and while it has even less information about the charset involved the process is similar to the -J case. - Note that we won't add decoding to -O without the user asking for it with + Note that we will not add decoding to -O without the user asking for it with some other means as well, since -O has always been documented to use the name exactly as specified in the URL. @@ -418,7 +418,7 @@ problems may have been fixed or changed somewhat since this was written! 4.3 --retry and transfer timeouts If using --retry and the transfer timeouts (possibly due to using -m or - -y/-Y) the next attempt doesn't resume the transfer properly from what was + -y/-Y) the next attempt does not resume the transfer properly from what was downloaded in the previous attempt but will truncate and restart at the original position where it was at before the previous failed attempt. See https://curl.se/mail/lib-2008-01/0080.html and Mandriva bug report @@ -466,13 +466,13 @@ problems may have been fixed or changed somewhat since this was written! We welcome help to improve curl's ability to link with static libraries, but it is likely a task that we can never fully support. -5.5 can't handle Unicode arguments in non-Unicode builds on Windows +5.5 cannot handle Unicode arguments in non-Unicode builds on Windows - If a URL or filename can't be encoded using the user's current codepage then + If a URL or filename cannot be encoded using the user's current codepage then it can only be encoded properly in the Unicode character set. Windows uses UTF-16 encoding for Unicode and stores it in wide characters, however curl and libcurl are not equipped for that at the moment except when built with - _UNICODE and UNICODE defined. And, except for Cygwin, Windows can't use UTF-8 + _UNICODE and UNICODE defined. And, except for Cygwin, Windows cannot use UTF-8 as a locale. https://curl.se/bug/?i=345 @@ -532,7 +532,7 @@ problems may have been fixed or changed somewhat since this was written! number of the Windows builds are flaky. This means that we rarely get all CI builds go green and complete without errors. This is unfortunate as it makes us sometimes miss actual build problems and it is surprising to newcomers to - the project who (rightfully) don't expect this. + the project who (rightfully) do not expect this. See https://github.com/curl/curl/issues/6972 @@ -573,7 +573,7 @@ problems may have been fixed or changed somewhat since this was written! new conn->bits.want_authentication which is set when any of the authentication options are set. -6.5 NTLM doesn't support password with § character +6.5 NTLM does not support password with § character https://github.com/curl/curl/issues/2120 @@ -583,12 +583,12 @@ problems may have been fixed or changed somewhat since this was written! authentication will cause libcurl to abort trying other options if the failed method has a higher preference than the alternatives. As an example, --proxy-any against a proxy which advertise Negotiate and NTLM, but which - fails to set up Kerberos authentication won't proceed to try authentication + fails to set up Kerberos authentication will not proceed to try authentication using NTLM. https://github.com/curl/curl/issues/876 -6.7 Don't clear digest for single realm +6.7 Do not clear digest for single realm https://github.com/curl/curl/issues/3267 @@ -614,7 +614,7 @@ problems may have been fixed or changed somewhat since this was written! 6.10 curl never completes Negotiate over HTTP - Apparently it isn't working correctly...? + Apparently it is not working correctly...? See https://github.com/curl/curl/issues/5235 @@ -626,7 +626,7 @@ problems may have been fixed or changed somewhat since this was written! https://github.com/curl/curl/issues/5881 -6.12 Can't use Secure Transport with Crypto Token Kit +6.12 cannot use Secure Transport with Crypto Token Kit https://github.com/curl/curl/issues/7048 @@ -645,7 +645,7 @@ problems may have been fixed or changed somewhat since this was written! 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 + data transfer is not 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. @@ -658,13 +658,13 @@ problems may have been fixed or changed somewhat since this was written! 7.4 FTP with ACCT When doing an operation over FTP that requires the ACCT command (but not when - logging in), the operation will fail since libcurl doesn't detect this and + logging in), the operation will fail since libcurl does not detect this and thus fails to issue the correct command: https://curl.se/bug/view.cgi?id=635 7.5 ASCII FTP - FTP ASCII transfers do not follow RFC959. They don't convert the data + FTP ASCII transfers do not follow RFC959. They do not convert the data accordingly (not for sending nor for receiving). RFC 959 section 3.1.1.1 clearly describes how this should be done: @@ -700,12 +700,12 @@ problems may have been fixed or changed somewhat since this was written! When 'multi_done' is called before the transfer has been completed the normal way, it is considered a "premature" transfer end. In this situation, libcurl - closes the connection assuming it doesn't know the state of the connection so - it can't be reused for subsequent requests. + closes the connection assuming it does not know the state of the connection so + it cannot be reused for subsequent requests. - With FTP however, this isn't necessarily true but there are a bunch of + With FTP however, this is not necessarily true but there are a bunch of situations (listed in the ftp_done code) where it *could* keep the connection - alive even in this situation - but the current code doesn't. Fixing this would + alive even in this situation - but the current code does not. Fixing this would allow libcurl to reuse FTP connections better. 7.9 Passive transfer tries only one IP address @@ -734,7 +734,7 @@ problems may have been fixed or changed somewhat since this was written! message. When curl closes the upload connection if unread data has been received (such as a TLS handshake message) then the TCP protocol sends an RST to the server, which may cause the server to discard or truncate the - upload if it hasn't read all sent data yet, and then return an error to curl + upload if it has not read all sent data yet, and then return an error to curl on the control channel connection. Since 7.78.0 this is mostly fixed. curl will do a single read before closing @@ -746,9 +746,9 @@ problems may have been fixed or changed somewhat since this was written! 8. TELNET -8.1 TELNET and time limitations don't work +8.1 TELNET and time limitations do not work - When using telnet, the time limitation options don't work. + When using telnet, the time limitation options do not work. https://curl.se/bug/view.cgi?id=846 8.2 Microsoft telnet server @@ -759,7 +759,7 @@ problems may have been fixed or changed somewhat since this was written! 9. SFTP and SCP -9.1 SFTP doesn't do CURLOPT_POSTQUOTE correct +9.1 SFTP does not do CURLOPT_POSTQUOTE correct When libcurl sends CURLOPT_POSTQUOTE commands when connected to a SFTP server using the multi interface, the commands are not being sent correctly and @@ -768,10 +768,10 @@ problems may have been fixed or changed somewhat since this was written! report but it cannot be accepted as-is. See https://curl.se/bug/view.cgi?id=748 -9.2 wolfssh: publickey auth doesn't work +9.2 wolfssh: publickey auth does not work When building curl to use the wolfSSH backend for SFTP, the publickey - authentication doesn't work. This is simply functionality not written for curl + authentication does not work. This is simply functionality not written for curl yet, the necessary API for make this work is provided by wolfSSH. See https://github.com/curl/curl/issues/4820 @@ -788,11 +788,11 @@ problems may have been fixed or changed somewhat since this was written! 10.3 FTPS over SOCKS - libcurl doesn't support FTPS over a SOCKS proxy. + libcurl does not support FTPS over a SOCKS proxy. 10.4 active FTP over a SOCKS - libcurl doesn't support active FTP over a SOCKS proxy + libcurl does not support active FTP over a SOCKS proxy 11. Internals @@ -812,14 +812,14 @@ problems may have been fixed or changed somewhat since this was written! CURLE_COULDNT_CONNECT. But the error buffer set by CURLOPT_ERRORBUFFER remains empty. Issue: https://github.com/curl/curl/issues/544 -11.3 Disconnects don't do verbose +11.3 Disconnects do not do verbose Due to how libcurl keeps connections alive in the "connection pool" after use to potentially transcend the life-time of the initial easy handle that was used to drive the transfer over that connection, it uses a *separate* and internal easy handle when it shuts down the connection. That separate connection might not have the exact same settings as the original easy - handle, and in particular it is often note-worthy that it doesn't have the + handle, and in particular it is often note-worthy that it does not have the same VERBOSE and debug callbacks setup so that an application will not get the protocol data for the disconnect phase of a transfer the same way it got all the other data. @@ -832,7 +832,7 @@ problems may have been fixed or changed somewhat since this was written! 11.4 HTTP test server 'connection-monitor' problems - The 'connection-monitor' feature of the sws HTTP test server doesn't work + The 'connection-monitor' feature of the sws HTTP test server does not work properly if some tests are run in unexpected order. Like 1509 and then 1525. See https://github.com/curl/curl/issues/868 @@ -853,7 +853,7 @@ problems may have been fixed or changed somewhat since this was written! HAPPY_EYEBALLS_TIMEOUT define exactly. Lowering that define speeds up the connection, suggesting a problem in the HE handling. - If we can *know* that we're talking to a local host, we should lower the + If we can *know* that we are talking to a local host, we should lower the happy eyeballs delay timeout for IPv6 (related: hardcode the "localhost" addresses, mentioned in TODO). Possibly we should reduce that delay for all. @@ -875,7 +875,7 @@ problems may have been fixed or changed somewhat since this was written! https://github.com/curl/curl/issues/4592 -11.9 DoH doesn't inherit all transfer options +11.9 DoH does not inherit all transfer options Some options are not inherited because they are not relevant for the DoH SSL connections, or inheriting the option may result in unexpected behavior. For @@ -903,7 +903,7 @@ problems may have been fixed or changed somewhat since this was written! 11.12 'no_proxy' string-matches IPv6 numerical addresses - This has the downside that "::1" for example doesn't match "::0:1" even + This has the downside that "::1" for example does not match "::0:1" even though they are in fact the same address. See https://github.com/curl/curl/issues/5745 @@ -972,7 +972,7 @@ problems may have been fixed or changed somewhat since this was written! https://github.com/curl/curl/issues/3116 -12.3 LDAP on Windows doesn't work +12.3 LDAP on Windows does not work A simple curl command line getting "ldap://ldap.forumsys.com" returns an error that says "no memory" ! @@ -988,7 +988,7 @@ problems may have been fixed or changed somewhat since this was written! 13.1 --interface for ipv6 binds to unusable IP address Since IPv6 provides a lot of addresses with different scope, binding to an - IPv6 address needs to take the proper care so that it doesn't bind to a + IPv6 address needs to take the proper care so that it does not bind to a locally scoped address as that is bound to fail. https://github.com/curl/curl/issues/686 @@ -997,7 +997,7 @@ problems may have been fixed or changed somewhat since this was written! 14.1 DICT responses show the underlying protocol - When getting a DICT response, the protocol parts of DICT aren't stripped off + When getting a DICT response, the protocol parts of DICT are not stripped off from the output. https://github.com/curl/curl/issues/1809 @@ -1019,13 +1019,13 @@ problems may have been fixed or changed somewhat since this was written! 15.4 build docs/curl.1 - The cmake build doesn't create the docs/curl.1 file and therefore must rely on + The cmake build does not create the docs/curl.1 file and therefore must rely on it being there already. This makes the --manual option not work and test - cases like 1139 can't function. + cases like 1139 cannot function. 15.5 build on Linux links libcurl to libdl - ... which it shouldn't need to! + ... which it should not need to! See https://github.com/curl/curl/issues/6165 @@ -1088,7 +1088,7 @@ problems may have been fixed or changed somewhat since this was written! This application crashes at startup with libcurl 7.74.0 (and presumably later versions too) after we cleaned up OpenSSL initialization. Since this is the only known application to do this, we suspect it is related to something they - are doing in their setup that isn't kosher. We have not been able to get in + are doing in their setup that is not kosher. We have not been able to get in contact with them nor got any technical details to help us debug this further. @@ -1163,12 +1163,12 @@ problems may have been fixed or changed somewhat since this was written! https://github.com/curl/curl/issues/7532 -18.8 HTTP/3 doesn't support client certs +18.8 HTTP/3 does not support client certs aka "mutual authentication". https://github.com/curl/curl/issues/7625 -18.9 connection migration doesn't work +18.9 connection migration does not work https://github.com/curl/curl/issues/7695 |