Lines Matching +full:ipv4 +full:- +full:multi +full:- +full:target
15 1.2 Multiple methods in a single WWW-Authenticate: header
18 1.5 Expect-100 meets 417
42 3.3 POP3 expects "CRLF.CRLF" eob for some single-line responses
46 4.1 -J and -O with %-encoded file names
47 4.2 -J with -C - fails
48 4.3 --retry and transfer timeouts
52 5.2 curl-config --libs contains private details
55 5.5 can't handle Unicode arguments in non-Unicode builds on Windows
60 5.11 configure --with-gssapi with Heimdal is ignored on macOS
69 6.6 libcurl can fail to try alternatives with --proxy-any
72 6.9 SHA-256 digest not supported in Windows SSPI builds
104 11.3 c-ares deviates from stock resolver on http://1346569778
105 11.4 HTTP test server 'connection-monitor' problems
108 11.7 signal-based resolver timeouts
111 11.10 Blocking socket operations in non-blocking API
112 11.11 A shared connection cache is not thread-safe
113 11.12 'no_proxy' string-matches IPv6 numerical addresses
115 11.14 Multi perform hangs waiting for threaded resolver
126 13.1 --interface for ipv6 binds to unusable IP address
137 15.6 uses -lpthread instead of Threads::Threads
140 15.9 cert paths autodetected when cross-compiling
163 1.2 Multiple methods in a single WWW-Authenticate: header
165 The HTTP responses headers WWW-Authenticate: can provide information about
186 https://tools.ietf.org/html/draft-reschke-rfc2231-in-http-02
188 1.5 Expect-100 meets 417
190 If an upload using Expect: 100-continue receives an HTTP 417 response, it
193 https://curl.se/mail/archive-2008-02/0043.html
198 waiting for the 100-continue response.
199 https://curl.se/mail/lib-2008-08/0462.html
257 server-specified DNs, the OpenSSL and GnuTLS backends behave differently.
264 Since libcurl 7.57.0, the flag CURL_GLOBAL_SSL is a no-op. The change was
276 C) libcurl uses some TLS backend functionality even for non-TLS functions (to
306 The GnuTLS `backend->cred` and the OpenSSL `backend->ctx` data and their
325 expires." - the same command line seems to work with other TLS backends and
356 3.3 POP3 expects "CRLF.CRLF" eob for some single-line responses
364 Specifying "--login-options AUTH=PLAIN" on the command line doesn't seem to
371 4.1 -J and -O with %-encoded file names
373 -J/--remote-header-name doesn't decode %-encoded file names. RFC6266 details
381 -O also doesn't decode %-encoded names, and while it has even less
382 information about the charset involved the process is similar to the -J case.
384 Note that we won't add decoding to -O without the user asking for it with
385 some other means as well, since -O has always been documented to use the name
388 4.2 -J with -C - fails
390 When using -J (with -O), automatically resumed downloading together with "-C
391 -" fails. Without -J the same command line works! This happens because the
392 resume logic is worked out before the target file name (and thus its
393 pre-transfer size) has been figured out!
396 4.3 --retry and transfer timeouts
398 If using --retry and the transfer timeouts (possibly due to using -m or
399 -y/-Y) the next attempt doesn't resume the transfer properly from what was
402 https://curl.se/mail/lib-2008-01/0080.html and Mandriva bug report
415 5.2 curl-config --libs contains private details
417 "curl-config --libs" will include details set in LDFLAGS when configure is
418 run that might be needed only for building libcurl. Further, curl-config
419 --cflags suffers from the same effects with CFLAGS/CPPFLAGS.
430 loader - on all modern systems.
447 5.5 can't handle Unicode arguments in non-Unicode builds on Windows
451 UTF-16 encoding for Unicode and stores it in wide characters, however curl
453 _UNICODE and UNICODE defined. And, except for Cygwin, Windows can't use UTF-8
465 - support for zlib and nghttp2
466 - use of static runtime libraries
467 - add the test suite components
471 - support for other development IDEs
472 - add PATH environment variables for third-party DLLs
476 When the configure script checks for third-party libraries, it adds those
501 5.11 configure --with-gssapi with Heimdal is ignored on macOS
503 ... unless you also pass --with-gssapi-libs
524 https://curl.se/mail/lib-2009-10/0024.html
528 https://curl.se/mail/lib-2012-07/0073.html
539 "system context" will make it use wrong(?) user name - at least when compared
545 V5 in the e-mail protocols, you need to provide a (fake) user name (this
548 conn->bits.user_passwd in url.c https://curl.se/bug/view.cgi?id=440 How?
549 https://curl.se/mail/lib-2004-08/0182.html A possible solution is to
551 new conn->bits.want_authentication which is set when any of the authentication
558 6.6 libcurl can fail to try alternatives with --proxy-any
560 When connecting via a proxy using --proxy-any, a failure to establish an
563 --proxy-any against a proxy which advertise Negotiate and NTLM, but which
575 RTSP authentication broke in 7.66.0. A work-around is to enable RTSP in
582 6.9 SHA-256 digest not supported in Windows SSPI builds
601 When using --negotiate (or NTLM) with curl on Windows, SSL/TSL handshake
614 connection timeout during that phase but only the "real" timeout - which may
621 When doing FTP over a socks proxy or CONNECT through HTTP proxy and the multi
631 https://curl.se/mail/lib-2008-07/0295.html
647 the standard 8-bit NVT-ASCII representation (see the Telnet
683 alive even in this situation - but the current code doesn't. Fixing this would
723 using the multi interface, the commands are not being sent correctly and
725 prematurely. There is a half-baked (busy-looping) patch provided in the bug
726 report but it cannot be accepted as-is. See
769 only. But you only have IPv4 connectivity. libcurl will correctly fail with
773 11.3 c-ares deviates from stock resolver on http://1346569778
780 but with c-ares it instead says "Could not resolve: 1346569778 (Domain name
785 11.4 HTTP test server 'connection-monitor' problems
787 The 'connection-monitor' feature of the sws HTTP test server doesn't work
803 both ipv4 and ipv6 and try to connect to both happy eyeballs-style. Something
804 in there does however make it take 200 milliseconds to succeed - which is the
814 11.7 signal-based resolver timeouts
820 non-portable and could cause problems on some platforms. A discussion on the
821 problem is available at https://curl.se/mail/lib-2008-09/0197.html
839 DoH without a DoH-specific option. For example: CURLOPT_DOH_SSL_VERIFYHOST,
844 11.10 Blocking socket operations in non-blocking API
846 The list of blocking socket operations is in TODO section "More non-blocking".
848 11.11 A shared connection cache is not thread-safe
852 still not thread-safe when used shared.
856 11.12 'no_proxy' string-matches IPv6 numerical addresses
875 11.14 Multi perform hangs waiting for threaded resolver
878 waiting for it for a longer time than expected - and longer than the set
895 For saving cookies, alt-svc and hsts files. This is bad when for example the
921 https://curl.se/mail/lib-2016-01/0101.html
940 13.1 --interface for ipv6 binds to unusable IP address
975 it being there already. This makes the --manual option not work and test
984 15.6 uses -lpthread instead of Threads::Threads
990 The Libs.private field of the generated .pc file contains -lgcc -lgcc_s -lc
991 -lgcc -lgcc_s
999 autotools equivalent would say Libs.private: -lssl -lcrypto -lz
1003 15.9 cert paths autodetected when cross-compiling
1006 cross-compiling. The cmake build keeps doing the detection.
1037 …https://community.pulsesecure.net/t5/Pulse-Desktop-Clients/Linux-Pulse-Client-does-not-work-with-c…