Lines Matching +full:srv +full:- +full:ipv6 +full:- +full:multi +full:- +full:target
23 1.4 signal-based resolver timeouts
29 1.10 auto-detect proxy
32 1.13 c-ares and CURLOPT_OPENSOCKETFUNCTION
39 1.20 SRV and URI DNS records
51 2. libcurl - multi interface
52 2.1 More non-blocking
54 2.3 Non-blocking curl_multi_remove_handle()
56 2.5 Edge-triggered sockets should work
57 2.6 multi upkeep
60 3.2 Provide cmake config-file
83 6.2 ditch telnet-specific select
113 13.3 Support in-memory certs/ca certs/keys
117 13.7 improve configure --with-ssl
132 15.3 Add support for the --ciphers option
133 15.4 Add option to disable client certificate auto-send
138 16.3 Support binary messages (i.e.: non-base64)
151 18.5 UTF-8 filenames in Content-Disposition
154 18.8 offer color-coded HTTP header output
160 18.14 --fail without --location should treat 3xx as a failure
161 18.15 --retry should resume
162 18.16 send only part of --data
163 18.17 consider file name from the redirected URL with -O ?
183 21.1 http-style HEAD output for FTP
216 To support IPv6 interface addresses for network interfaces properly.
218 1.4 signal-based resolver timeouts
224 non-portable and could cause problems on some platforms. A discussion on the
225 problem is available at https://curl.haxx.se/mail/lib-2008-09/0197.html
233 https://insanecoding.blogspot.com/2007/11/pathmax-simply-isnt.html
277 1.10 auto-detect proxy
282 The pull-request to use libproxy for this was deferred due to doubts on the
291 We can create a system with loadable modules/plug-ins, where these modules
307 1.13 c-ares and CURLOPT_OPENSOCKETFUNCTION
310 close them with the CURLOPT_CLOSESOCKETFUNCTION callback. However, c-ares
312 itself. This means that when curl passes the c-ares socket to the
326 curl_easy_set_num() - sets a long value
328 curl_easy_set_large() - sets a curl_off_t value
330 curl_easy_set_ptr() - sets a pointer
332 curl_easy_set_cb() - sets a callback PLUS its callback data
359 IRIs (RFC 3987) allow localized, non-ascii, names in the URL. To properly
385 1.20 SRV and URI DNS records
387 Offer support for resolving SRV and URI DNS records for libcurl to know which
423 cleartext network protocol. That's all non-encrypted ones (FTP, HTTP, Gopher,
425 variable can then help users to block all libcurl-using programs from
439 fine way for curl to fix this would be to simply hard-code the response to
445 https://tools.ietf.org/html/draft-ietf-dnsop-let-localhost-be-localhost-02
449 It sets the close-on-exec flag for the file descriptor, which causes the file
451 exec-family functions succeed. Should probably be set by default?
461 …https://curl.haxx.se/video/curlup-2017/2017-03-19_05_Michael_Kaufmann_Websocket_support_for_curl.m…
466 parsing a config file like curl's -K/--config option to allow applications to
471 2. libcurl - multi interface
473 2.1 More non-blocking
475 Make sure we don't ever loop because of non-blocking sockets returning
478 - Name resolves on non-windows unless c-ares or the threaded resolver is used
479 - SOCKS proxy handshakes
480 - file:// transfers
481 - TELNET transfers
482 - The "DONE" operation (post transfer protocol-specific actions) for the
493 2.3 Non-blocking curl_multi_remove_handle()
495 The multi interface has a few API calls that assume a blocking behavior, like
497 multi API need to be moved even more into a single function that "drives"
498 everything in a non-blocking manner and signals when something is done. A
504 The multi interface treats the authentication process as part of the connect
508 2.5 Edge-triggered sockets should work
510 The multi_socket API should work with edge-triggered socket events. One of
514 2.6 multi upkeep
517 on easy handles. We should introduces a version of that for the multi handle,
519 connection pool when the multi handle is in used.
525 3.2 Provide cmake config-file
527 A config-file package is a set of files provided by us to allow applications
536 servers named-based virtual hosting:
566 via third-party GSS-API libraries, such as Heimdal or MIT Kerberos, also add
624 http://test:pass;auth=NTLM@example.com would be equivalent to specifying --user
625 test:pass;auth=NTLM or --user test:pass --ntlm from the command line.
655 6.2 ditch telnet-specific select
658 into the main transfer loop. Until this is done, the multi interface won't
681 specifying this data as the URL is non-standard and to be honest a bit of a
682 hack ;-)
685 https://curl.haxx.se/mail/lib-2012-05/0178.html
734 that doesn't exist on the server, just like --ftp-create-dirs.
753 library, so that the same application code can use mutex-locking
756 13.3 Support in-memory certs/ca certs/keys
759 programs want to avoid using files and instead just pass them as in-memory
766 "Look at SSL cafile - quick traces look to me like these are done on every
770 instead make one for every connection and re-use that SSL context in the same
771 style connections are re-used. It will make us use slightly more memory but
785 the state from such a buffer at a later date - this is used by mod_ssl for
794 13.7 improve configure --with-ssl
796 make the configure --with-ssl option first check for OpenSSL, then GnuTLS,
801 DNS-Based Authentication of Named Entities (DANE) is a way to provide SSL
803 https://www.rfc-editor.org/rfc/rfc6698.txt
806 (https://curl.haxx.se/mail/lib-2013-03/0075.html) but it was a too simple
808 https://curl.haxx.se/mail/lib-2013-03/0103.html . libunbound may be the
849 "HTTP Strict Transport Security" is TOFU (trust on first use), time-based
854 Doc: https://developer.mozilla.org/en-US/docs/Web/Security/HTTP_strict_transport_security
859 "HTTP Public Key Pinning" is TOFU (trust on first use), time-based
861 to prevent Man-in-the-middle attacks by trusted CAs by allowing webadmins
870 RFC: https://tools.ietf.org/html/draft-ietf-websec-key-pinning-21
897 WinSSL/SChannel currently makes use of the OS-level system and user
901 Therefore support for the existing -E/--cert and --key options should be
903 - Getting a Certificate for Schannel
904 https://msdn.microsoft.com/en-us/library/windows/desktop/aa375447.aspx
906 15.3 Add support for the --ciphers option
908 The cipher suites used by WinSSL/SChannel are configured on an OS-level
909 instead of an application-level. This does not allow the application or
912 Therefore support for the existing --ciphers option should be implemented
914 - Specifying Schannel Ciphers and Cipher Strengths
915 https://msdn.microsoft.com/en-us/library/windows/desktop/aa380161.aspx
917 15.4 Add option to disable client certificate auto-send
926 Schannel auto-send behavior.
935 GSS-SPNEGO and others.
940 (Authentication), whilst Kerberos V5 supports both auth-int (Authentication
941 with integrity protection) and auth-conf (Authentication with integrity and
944 16.3 Support binary messages (i.e.: non-base64)
972 underlying functionality and it supports at least SHA-1 as an alternative.
973 SHA-1 is also being deprecated these days so we should consider working with
974 libssh2 to instead offer support for SHA-256 or similar.
985 "curl --sync http://example.com/feed[1-100].rss" or
986 "curl --sync http://example.net/{index,calendar,history}.html"
989 remote file is newer than the local file. A Last-Modified HTTP date header
994 Globbing support for -d and -F, as in 'curl -d "name=foo[0-9]" URL'.
1000 used, and there already is an existing file with the target file name
1001 (either -O or -o), a number should be appended (and increased if already
1010 multi interface. https://curl.haxx.se/bug/feature.cgi?id=1558595
1012 Using the multi interface would also allow properly using parallel transfers
1015 18.5 UTF-8 filenames in Content-Disposition
1017 RFC 6266 documents how UTF-8 names can be passed to a client in the
1018 Content-Disposition header, and curl does not support this.
1035 18.8 offer color-coded HTTP header output
1081 downloading the target of the metalink. This is done via the --metalink option.
1084 also be supported with the --metalink option.
1088 See also https://lists.gnu.org/archive/html/bug-wget/2015-06/msg00034.html for
1091 18.14 --fail without --location should treat 3xx as a failure
1096 curl -v --fail -O https://example.com/curl-7.48.0.tar.gz
1098 ... --fail must treat 3xx responses as failures too. The least problematic
1102 18.15 --retry should resume
1104 When --retry is used and curl actually retries transfer, it should use the
1111 18.16 send only part of --data
1114 --data or --data-binary, like when that data is a huge file, consider a way
1116 would be: "--data-binary @largefile.zip!1073741823-2147483647".
1120 18.17 consider file name from the redirected URL with -O ?
1122 When a user gives a URL and uses -O, and curl follows a redirect to a new
1123 URL, the file name is not extracted and used from the newly redirected-to URL
1128 could allow for this or maybe -J should imply such a treatment as well as -J
1141 The --retry option retries transfers on "transient failures". We later added
1142 --retry-connrefused to also retry for "connection refused" errors.
1161 default .curlrc could a specific user-agent only when doing requests against
1178 different binary sections like the GOT as read-only and thus kills a handful
1188 about it) nor does it support running the test suite if building out-of-tree.
1197 and FTP-SSL tests without the stunnel dependency, and it could allow us to
1218 used when using different login credentials in protocols that shouldn't re-use
1225 been dropped (unless it has been forced - which we shouldn't do in these tests)
1232 https://github.com/abarth/http-state/tree/master/tests
1246 21.1 http-style HEAD output for FTP
1248 #undef CURL_FTP_HTTPSTYLE_HEAD in lib/ftp.c to remove the HTTP-style headers
1310 They will instead become curlx_ - alternatives. That makes the curl app