[gnurl] 18/18: Merge branch 'master' of https://github.com/curl/curl

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnurl.

commit 71b588320daebd4e50603602c311bbed97755e27
Merge: 486ada36f 525787269
Author: ng0 <address@hidden>
AuthorDate: Fri Dec 20 13:45:46 2019 +0000

    Merge branch 'master' of https://github.com/curl/curl

 RELEASE-NOTES                          | 71 +++++++++++++++++++++++++++-------
 docs/HISTORY.md                        |  4 ++
 docs/examples/url2file.c               |  2 +-
 docs/libcurl/opts/GNURLOPT_POSTQUOTE.3 |  8 ++--
 docs/libcurl/opts/GNURLOPT_PREQUOTE.3  |  6 +--
 docs/libcurl/opts/GNURLOPT_QUOTE.3     |  8 ++--
 docs/libcurl/opts/GNURLOPT_URL.3       |  4 +-
 include/gnurl/curl.h                   |  2 +
 lib/strerror.c                         |  2 +-
 lib/url.c                              | 18 ---------
 lib/vquic/ngtcp2.c                     | 31 +--------------
 lib/vquic/ngtcp2.h                     |  3 --
 src/tool_parsecfg.c                    |  4 +-
 tests/data/Makefile.inc                |  2 +-
 tests/data/test1270                    | 69 +++++++++++++++++++++++++++++++++
 tests/data/test1448                    |  2 +-
 tests/data/test1455                    |  3 +-
 tests/data/test1456                    | 10 ++++-
 tests/data/test165                     |  2 +-
 tests/data/test2046                    |  2 +-
 tests/data/test2047                    |  2 +-
 tests/server/sws.c                     | 40 +++++++++++--------
 22 files changed, 190 insertions(+), 105 deletions(-)

diff --cc docs/libcurl/opts/GNURLOPT_POSTQUOTE.3
index c87d3fdc1,000000000..f4ebeb00a
mode 100644,000000..100644
--- a/docs/libcurl/opts/GNURLOPT_POSTQUOTE.3
+++ b/docs/libcurl/opts/GNURLOPT_POSTQUOTE.3
@@@ -1,64 -1,0 +1,64 @@@
 +.\" **************************************************************************
 +.\" *                                  _   _ ____  _
 +.\" *  Project                     ___| | | |  _ \| |
 +.\" *                             / __| | | | |_) | |
 +.\" *                            | (__| |_| |  _ <| |___
 +.\" *                             \___|\___/|_| \_\_____|
 +.\" *
 +.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <address@hidden>, et al.
 +.\" *
 +.\" * This software is licensed as described in the file COPYING, which
 +.\" * you should have received as part of this distribution. The terms
 +.\" * are also available at https://curl.haxx.se/docs/copyright.html.
 +.\" *
 +.\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
 +.\" * copies of the Software, and permit persons to whom the Software is
 +.\" * furnished to do so, under the terms of the COPYING file.
 +.\" *
 +.\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF 
ANY
 +.\" * KIND, either express or implied.
 +.\" *
 +.\" **************************************************************************
 +.\"
 +.TH GNURLOPT_POSTQUOTE 3 "17 Jun 2014" "libcurl 7.37.0" "curl_easy_setopt 
options"
 +.SH NAME
 +CURLOPT_POSTQUOTE \- (S)FTP commands to run after the transfer
 +.SH SYNOPSIS
 +#include <gnurl/curl.h>
 +
 +CURLcode curl_easy_setopt(CURL *handle, CURLOPT_POSTQUOTE, struct curl_slist 
*cmds);
 +.SH DESCRIPTION
 +Pass a pointer to a linked list of FTP or SFTP commands to pass to the server
 +after your FTP transfer request. The commands will only be run if no error
 +occurred. The linked list should be a fully valid list of struct curl_slist
 +structs properly filled in as described for \fICURLOPT_QUOTE(3)\fP.
 +
 +Disable this operation again by setting a NULL to this option.
 +.SH DEFAULT
 +NULL
 +.SH PROTOCOLS
 +SFTP and FTP
 +.SH EXAMPLE
 +.nf
- struct curl_slist *h = NULL;
- h = curl_slist_append(h, "RNFR source-name");
- h = curl_slist_append(h, "RNTO new-name");
++struct curl_slist *cmdlist = NULL;
++cmdlist = curl_slist_append(cmdlist, "RNFR source-name");
++cmdlist = curl_slist_append(cmdlist, "RNTO new-name");
 +
 +curl = curl_easy_init();
 +if(curl) {
 +  curl_easy_setopt(curl, CURLOPT_URL, "ftp://example.com/foo.bin";);
 +
 +  /* pass in the FTP commands to run after the transfer */
-   curl_easy_setopt(curl, CURLOPT_POSTQUOTE, headerlist);
++  curl_easy_setopt(curl, CURLOPT_POSTQUOTE, cmdlist);
 +
 +  ret = curl_easy_perform(curl);
 +
 +  curl_easy_cleanup(curl);
 +}
 +.fi
 +.SH AVAILABILITY
 +If support for the protocols are built-in.
 +.SH RETURN VALUE
 +Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
 +.SH "SEE ALSO"
 +.BR CURLOPT_QUOTE "(3), " CURLOPT_PREQUOTE "(3), "
diff --cc docs/libcurl/opts/GNURLOPT_PREQUOTE.3
index 80f23ff3e,000000000..10bb993a6
mode 100644,000000..100644
--- a/docs/libcurl/opts/GNURLOPT_PREQUOTE.3
+++ b/docs/libcurl/opts/GNURLOPT_PREQUOTE.3
@@@ -1,66 -1,0 +1,66 @@@
 +.\" **************************************************************************
 +.\" *                                  _   _ ____  _
 +.\" *  Project                     ___| | | |  _ \| |
 +.\" *                             / __| | | | |_) | |
 +.\" *                            | (__| |_| |  _ <| |___
 +.\" *                             \___|\___/|_| \_\_____|
 +.\" *
 +.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <address@hidden>, et al.
 +.\" *
 +.\" * This software is licensed as described in the file COPYING, which
 +.\" * you should have received as part of this distribution. The terms
 +.\" * are also available at https://curl.haxx.se/docs/copyright.html.
 +.\" *
 +.\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
 +.\" * copies of the Software, and permit persons to whom the Software is
 +.\" * furnished to do so, under the terms of the COPYING file.
 +.\" *
 +.\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF 
ANY
 +.\" * KIND, either express or implied.
 +.\" *
 +.\" **************************************************************************
 +.\"
 +.TH GNURLOPT_PREQUOTE 3 "17 Jun 2014" "libcurl 7.37.0" "curl_easy_setopt 
options"
 +.SH NAME
 +CURLOPT_PREQUOTE \- commands to run before an FTP transfer
 +.SH SYNOPSIS
 +#include <gnurl/curl.h>
 +
 +CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PREQUOTE,
 +                          struct curl_slist *cmds);
 +.SH DESCRIPTION
 +Pass a pointer to a linked list of FTP commands to pass to the server after
 +the transfer type is set. The linked list should be a fully valid list of
 +struct curl_slist structs properly filled in as described for
 +\fICURLOPT_QUOTE(3)\fP. Disable this operation again by setting a NULL to this
 +option.
 +
 +While \fICURLOPT_QUOTE(3)\fP and \fICURLOPT_POSTQUOTE(3)\fP work for SFTP,
 +this option does not.
 +.SH DEFAULT
 +NULL
 +.SH PROTOCOLS
 +FTP
 +.SH EXAMPLE
 +.nf
- struct curl_slist *h = NULL;
- h = curl_slist_append(h, "SYST");
++struct curl_slist *cmdlist = NULL;
++cmdlist = curl_slist_append(cmdlist, "SYST");
 +
 +curl = curl_easy_init();
 +if(curl) {
 +  curl_easy_setopt(curl, CURLOPT_URL, "ftp://example.com/foo.bin";);
 +
 +  /* pass in the FTP commands to run */
-   curl_easy_setopt(curl, CURLOPT_PREQUOTE, headerlist);
++  curl_easy_setopt(curl, CURLOPT_PREQUOTE, cmdlist);
 +
 +  ret = curl_easy_perform(curl);
 +
 +  curl_easy_cleanup(curl);
 +}
 +.fi
 +.SH AVAILABILITY
 +Along with the protocol support
 +.SH RETURN VALUE
 +Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
 +.SH "SEE ALSO"
 +.BR CURLOPT_QUOTE "(3), " CURLOPT_POSTQUOTE "(3), "
diff --cc docs/libcurl/opts/GNURLOPT_QUOTE.3
index 31c6dbff6,000000000..7740d1d6a
mode 100644,000000..100644
--- a/docs/libcurl/opts/GNURLOPT_QUOTE.3
+++ b/docs/libcurl/opts/GNURLOPT_QUOTE.3
@@@ -1,105 -1,0 +1,105 @@@
 +.\" **************************************************************************
 +.\" *                                  _   _ ____  _
 +.\" *  Project                     ___| | | |  _ \| |
 +.\" *                             / __| | | | |_) | |
 +.\" *                            | (__| |_| |  _ <| |___
 +.\" *                             \___|\___/|_| \_\_____|
 +.\" *
 +.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, <address@hidden>, et al.
 +.\" *
 +.\" * This software is licensed as described in the file COPYING, which
 +.\" * you should have received as part of this distribution. The terms
 +.\" * are also available at https://curl.haxx.se/docs/copyright.html.
 +.\" *
 +.\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
 +.\" * copies of the Software, and permit persons to whom the Software is
 +.\" * furnished to do so, under the terms of the COPYING file.
 +.\" *
 +.\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF 
ANY
 +.\" * KIND, either express or implied.
 +.\" *
 +.\" **************************************************************************
 +.\"
 +.TH GNURLOPT_QUOTE 3 "17 Jun 2014" "libcurl 7.37.0" "curl_easy_setopt options"
 +.SH NAME
 +CURLOPT_QUOTE \- (S)FTP commands to run before transfer
 +.SH SYNOPSIS
 +#include <gnurl/curl.h>
 +
 +CURLcode curl_easy_setopt(CURL *handle, CURLOPT_QUOTE, struct curl_slist 
*cmds);
 +.SH DESCRIPTION
 +Pass a pointer to a linked list of FTP or SFTP commands to pass to the server
 +prior to your request. This will be done before any other commands are issued
 +(even before the CWD command for FTP). The linked list should be a fully valid
 +list of 'struct curl_slist' structs properly filled in with text strings. Use
 +\fIcurl_slist_append(3)\fP to append strings (commands) to the list, and clear
 +the entire list afterwards with \fIcurl_slist_free_all(3)\fP. Disable this
 +operation again by setting a NULL to this option. When speaking to an FTP
 +server, prefix the command with an asterisk (*) to make libcurl continue even
 +if the command fails as by default libcurl will stop at first failure.
 +
 +The set of valid FTP commands depends on the server (see RFC959 for a list of
 +mandatory commands).
 +
 +The valid SFTP commands are:
 +.RS
 +.IP "chgrp group file"
 +The chgrp command sets the group ID of the file named by the file operand to
 +the group ID specified by the group operand. The group operand is a decimal
 +integer group ID.
 +.IP "chmod mode file"
 +The chmod command modifies the file mode bits of the specified file. The
 +mode operand is an octal integer mode number.
 +.IP "chown user file"
 +The chown command sets the owner of the file named by the file operand to the
 +user ID specified by the user operand. The user operand is a decimal
 +integer user ID.
 +.IP "ln source_file target_file"
 +The ln and symlink commands create a symbolic link at the target_file location
 +pointing to the source_file location.
 +.IP "mkdir directory_name"
 +The mkdir command creates the directory named by the directory_name operand.
 +.IP "pwd"
 +The pwd command returns the absolute pathname of the current working 
directory.
 +.IP "rename source target"
 +The rename command renames the file or directory named by the source
 +operand to the destination path named by the target operand.
 +.IP "rm file"
 +The rm command removes the file specified by the file operand.
 +.IP "rmdir directory"
 +The rmdir command removes the directory entry specified by the directory
 +operand, provided it is empty.
 +.IP "statvfs file"
 +The statvfs command returns statistics on the file system in which specified
 +file resides. (Added in 7.49.0)
 +.IP "symlink source_file target_file"
 +See ln.
 +.RE
 +.SH DEFAULT
 +NULL
 +.SH PROTOCOLS
 +SFTP and FTP
 +.SH EXAMPLE
 +.nf
- struct curl_slist *h = NULL;
- h = curl_slist_append(h, "RNFR source-name");
- h = curl_slist_append(h, "RNTO new-name");
++struct curl_slist *cmdlist = NULL;
++cmdlist = curl_slist_append(cmdlist, "RNFR source-name");
++cmdlist = curl_slist_append(cmdlist, "RNTO new-name");
 +
 +curl = curl_easy_init();
 +if(curl) {
 +  curl_easy_setopt(curl, CURLOPT_URL, "ftp://example.com/foo.bin";);
 +
 +  /* pass in the FTP commands to run before the transfer */
-   curl_easy_setopt(curl, CURLOPT_QUOTE, headerlist);
++  curl_easy_setopt(curl, CURLOPT_QUOTE, cmdlist);
 +
 +  ret = curl_easy_perform(curl);
 +
 +  curl_easy_cleanup(curl);
 +}
 +.fi
 +.SH AVAILABILITY
 +SFTP support added in 7.16.3. *-prefix for SFTP added in 7.24.0
 +.SH RETURN VALUE
 +Returns CURLE_OK
 +.SH "SEE ALSO"
 +.BR CURLOPT_POSTQUOTE "(3), " CURLOPT_PREQUOTE "(3), "
diff --cc docs/libcurl/opts/GNURLOPT_URL.3
index 6b377e4c7,000000000..473ea4f8a
mode 100644,000000..100644
--- a/docs/libcurl/opts/GNURLOPT_URL.3
+++ b/docs/libcurl/opts/GNURLOPT_URL.3
@@@ -1,356 -1,0 +1,356 @@@
 +.\" **************************************************************************
 +.\" *                                  _   _ ____  _
 +.\" *  Project                     ___| | | |  _ \| |
 +.\" *                             / __| | | | |_) | |
 +.\" *                            | (__| |_| |  _ <| |___
 +.\" *                             \___|\___/|_| \_\_____|
 +.\" *
- .\" * Copyright (C) 1998 - 2018, Daniel Stenberg, <address@hidden>, et al.
++.\" * Copyright (C) 1998 - 2019, Daniel Stenberg, <address@hidden>, et al.
 +.\" *
 +.\" * This software is licensed as described in the file COPYING, which
 +.\" * you should have received as part of this distribution. The terms
 +.\" * are also available at https://curl.haxx.se/docs/copyright.html.
 +.\" *
 +.\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
 +.\" * copies of the Software, and permit persons to whom the Software is
 +.\" * furnished to do so, under the terms of the COPYING file.
 +.\" *
 +.\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF 
ANY
 +.\" * KIND, either express or implied.
 +.\" *
 +.\" **************************************************************************
 +.\"
 +.TH GNURLOPT_URL 3 "17 Jun 2014" "libcurl 7.37.0" "curl_easy_setopt options"
 +.SH NAME
 +CURLOPT_URL \- provide the URL to use in the request
 +.SH SYNOPSIS
 +#include <gnurl/curl.h>
 +
 +CURLcode curl_easy_setopt(CURL *handle, CURLOPT_URL, char *URL);
 +.SH DESCRIPTION
 +Pass in a pointer to the \fIURL\fP to work with. The parameter should be a
 +char * to a zero terminated string which must be URL-encoded in the following
 +format:
 +
 +scheme://host:port/path
 +
 +For a greater explanation of the format please see RFC3986.
 +
 +libcurl doesn't validate the syntax or use this variable until the transfer is
 +issued. Even if you set a crazy value here, \fIcurl_easy_setopt(3)\fP will
 +still return \fICURLE_OK\fP.
 +
 +If the given URL is missing a scheme name (such as "http://"; or "ftp://"; etc)
 +then libcurl will make a guess based on the host. If the outermost sub-domain
 +name matches DICT, FTP, IMAP, LDAP, POP3 or SMTP then that protocol will be
 +used, otherwise HTTP will be used. Since 7.45.0 guessing can be disabled by
 +setting a default protocol, see \fICURLOPT_DEFAULT_PROTOCOL(3)\fP for details.
 +
 +Should the protocol, either that specified by the scheme or deduced by libcurl
 +from the host name, not be supported by libcurl then
 +\fICURLE_UNSUPPORTED_PROTOCOL\fP will be returned from either the
 +\fIcurl_easy_perform(3)\fP or \fIcurl_multi_perform(3)\fP functions when you
 +call them. Use \fIcurl_version_info(3)\fP for detailed information of which
 +protocols are supported by the build of libcurl you are using.
 +
 +\fICURLOPT_PROTOCOLS(3)\fP can be used to limit what protocols libcurl will
 +use for this transfer, independent of what libcurl has been compiled to
 +support. That may be useful if you accept the URL from an external source and
 +want to limit the accessibility.
 +
 +The \fICURLOPT_URL(3)\fP string will be ignored if \fICURLOPT_CURLU(3)\fP is
 +set.
 +
 +\fICURLOPT_URL(3)\fP or \fICURLOPT_CURLU(3)\fP \fBmust\fP be set before a
 +transfer is started.
 +
 +The host part of the URL contains the address of the server that you want to
 +connect to. This can be the fully qualified domain name of the server, the
 +local network name of the machine on your network or the IP address of the
 +server or machine represented by either an IPv4 or IPv6 address. For example:
 +
 +http://www.example.com/
 +
 +http://hostname/
 +
 +http://192.168.0.1/
 +
 +http://[2001:1890:1112:1::20]/
 +
 +It is also possible to specify the user name, password and any supported login
 +options as part of the host, for the following protocols, when connecting to
 +servers that require authentication:
 +
 +http://user:address@hidden
 +
 +ftp://user:address@hidden
 +
 +smb://domain%2fuser:address@hidden
 +
 +imap://user:password;address@hidden
 +
 +pop3://user:password;address@hidden
 +
 +smtp://user:password;address@hidden
 +
 +At present only IMAP, POP3 and SMTP support login options as part of the host.
 +For more information about the login options in URL syntax please see RFC2384,
 +RFC5092 and IETF draft draft-earhart-url-smtp-00.txt (Added in 7.31.0).
 +
 +The port is optional and when not specified libcurl will use the default port
 +based on the determined or specified protocol: 80 for HTTP, 21 for FTP and 25
 +for SMTP, etc. The following examples show how to specify the port:
 +
 +http://www.example.com:8080/ - This will connect to a web server using port
 +8080 rather than 80.
 +
 +smtp://mail.example.com:587/ - This will connect to a SMTP server on the
 +alternative mail port.
 +
 +The path part of the URL is protocol specific and whilst some examples are
 +given below this list is not conclusive:
 +
 +.IP HTTP
 +The path part of an HTTP request specifies the file to retrieve and from what
 +directory. If the directory is not specified then the web server's root
 +directory is used. If the file is omitted then the default document will be
 +retrieved for either the directory specified or the root directory. The exact
 +resource returned for each URL is entirely dependent on the server's
 +configuration.
 +
 +http://www.example.com - This gets the main page from the web server.
 +
 +http://www.example.com/index.html - This returns the main page by explicitly
 +requesting it.
 +
 +http://www.example.com/contactus/ - This returns the default document from
 +the contactus directory.
 +
 +.IP FTP
 +The path part of an FTP request specifies the file to retrieve and from what
 +directory. If the file part is omitted then libcurl downloads the directory
 +listing for the directory specified. If the directory is omitted then
 +the directory listing for the root / home directory will be returned.
 +
 +ftp://ftp.example.com - This retrieves the directory listing for the root
 +directory.
 +
 +ftp://ftp.example.com/readme.txt - This downloads the file readme.txt from the
 +root directory.
 +
 +ftp://ftp.example.com/libcurl/readme.txt - This downloads readme.txt from the
 +libcurl directory.
 +
 +ftp://user:address@hidden/readme.txt - This retrieves the readme.txt
 +file from the user's home directory. When a username and password is
 +specified, everything that is specified in the path part is relative to the
 +user's home directory. To retrieve files from the root directory or a
 +directory underneath the root directory then the absolute path must be
 +specified by prepending an additional forward slash to the beginning of the
 +path.
 +
 +ftp://user:address@hidden//readme.txt - This retrieves the readme.txt
 +from the root directory when logging in as a specified user.
 +
 +.IP SMTP
 +The path part of a SMTP request specifies the host name to present during
 +communication with the mail server. If the path is omitted then libcurl will
 +attempt to resolve the local computer's host name. However, this may not
 +return the fully qualified domain name that is required by some mail servers
 +and specifying this path allows you to set an alternative name, such as
 +your machine's fully qualified domain name, which you might have obtained
 +from an external function such as gethostname or getaddrinfo.
 +
 +smtp://mail.example.com - This connects to the mail server at example.com and
 +sends your local computer's host name in the HELO / EHLO command.
 +
 +smtp://mail.example.com/client.example.com - This will send 
client.example.com in
 +the HELO / EHLO command to the mail server at example.com.
 +
 +.IP POP3
 +The path part of a POP3 request specifies the message ID to retrieve. If the
 +ID is not specified then a list of waiting messages is returned instead.
 +
 +pop3://user:address@hidden - This lists the available messages for
 +the user
 +
 +pop3://user:address@hidden/1 - This retrieves the first message for
 +the user
 +
 +.IP IMAP
 +The path part of an IMAP request not only specifies the mailbox to list (Added
 +in 7.30.0) or select, but can also be used to check the UIDVALIDITY of the
 +mailbox, to specify the UID, SECTION (Added in 7.30.0) and PARTIAL octets
 +(Added in 7.37.0) of the message to fetch and to specify what messages to
 +search for (Added in 7.37.0).
 +
 +imap://user:address@hidden - Performs a top level folder list
 +
 +imap://user:address@hidden/INBOX - Performs a folder list on the
 +user's inbox
 +
 +imap://user:address@hidden/INBOX/;UID=1 - Selects the user's inbox
 +and fetches message with uid = 1
 +
 +imap://user:address@hidden/INBOX/;MAILINDEX=1 - Selects the user's inbox
 +and fetches the first message in the mail box
 +
 +imap://user:address@hidden/INBOX;UIDVALIDITY=50/;UID=2 - Selects
 +the user's inbox, checks the UIDVALIDITY of the mailbox is 50 and fetches
 +message 2 if it is
 +
 +imap://user:address@hidden/INBOX/;UID=3/;SECTION=TEXT - Selects the
 +user's inbox and fetches the text portion of message 3
 +
 +imap://user:address@hidden/INBOX/;UID=4/;PARTIAL=0.1024 - Selects
 +the user's inbox and fetches the first 1024 octets of message 4
 +
 +imap://user:address@hidden/INBOX?NEW - Selects the user's inbox and
 +checks for NEW messages
 +
 +imap://user:address@hidden/INBOX?SUBJECT%20shadows - Selects the
 +user's inbox and searches for messages containing "shadows" in the subject
 +line
 +
 +For more information about the individual components of an IMAP URL please
 +see RFC5092.
 +
 +.IP SCP
 +The path part of a SCP request specifies the file to retrieve and from what
 +directory. The file part may not be omitted. The file is taken as an absolute
 +path from the root directory on the server. To specify a path relative to the
 +user's home directory on the server, prepend ~/ to the path portion.  If the
 +user name is not embedded in the URL, it can be set with the
 +\fICURLOPT_USERPWD(3)\fP or \fICURLOPT_USERNAME(3)\fP option.
 +
 +scp://address@hidden/etc/issue - This specifies the file /etc/issue
 +
 +scp://example.com/~/my-file - This specifies the file my-file in the
 +user's home directory on the server
- 
 +.IP SFTP
 +The path part of a SFTP request specifies the file to retrieve and from what
 +directory. If the file part is omitted then libcurl downloads the directory
 +listing for the directory specified.  If the path ends in a / then a directory
 +listing is returned instead of a file.  If the path is omitted entirely then
 +the directory listing for the root / home directory will be returned.  If the
 +user name is not embedded in the URL, it can be set with the
 +\fICURLOPT_USERPWD(3)\fP or \fICURLOPT_USERNAME(3)\fP option.
 +
 +sftp://user:address@hidden/etc/issue - This specifies the file
 +/etc/issue
 +
 +sftp://address@hidden/~/my-file - This specifies the file my-file in the
 +user's home directory
 +
 +sftp://ssh.example.com/~/Documents/ - This requests a directory listing
 +of the Documents directory under the user's home directory
 +
 +.IP SMB
 +The path part of a SMB request specifies the file to retrieve and from what
 +share and directory or the share to upload to and as such, may not be omitted.
 +If the user name is not embedded in the URL, it can be set with the
 +\fICURLOPT_USERPWD(3)\fP or \fICURLOPT_USERNAME(3)\fP option. If the user name
 +is embedded in the URL then it must contain the domain name and as such, the
 +backslash must be URL encoded as %2f.
 +
 +smb://server.example.com/files/issue - This specifies the file "issue" located
 +in the root of the "files" share
 +
 +smb://server.example.com/files/ -T issue - This specifies the file "issue" 
will
 +be uploaded to the root of the "files" share.
 +
++curl supports SMB version 1 (only)
 +.IP LDAP
 +The path part of a LDAP request can be used to specify the: Distinguished
 +Name, Attributes, Scope, Filter and Extension for a LDAP search. Each field
 +is separated by a question mark and when that field is not required an empty
 +string with the question mark separator should be included.
 +
 +ldap://ldap.example.com/o=My%20Organisation - This will perform a LDAP search
 +with the DN as My Organisation.
 +
 +ldap://ldap.example.com/o=My%20Organisation?postalAddress - This will perform
 +the same search but will only return postalAddress attributes.
 +
 +ldap://ldap.example.com/?rootDomainNamingContext - This specifies an empty DN
 +and requests information about the rootDomainNamingContext attribute for an
 +Active Directory server.
 +
 +For more information about the individual components of a LDAP URL please
 +see RFC4516.
 +.IP RTMP
 +There's no official URL spec for RTMP so libcurl uses the URL syntax supported
 +by the underlying librtmp library. It has a syntax where it wants a
 +traditional URL, followed by a space and a series of space-separated
 +name=value pairs.
 +
 +While space is not typically a "legal" letter, libcurl accepts them. When a
 +user wants to pass in a '#' (hash) character it will be treated as a fragment
 +and get cut off by libcurl if provided literally. You will instead have to
 +escape it by providing it as backslash and its ASCII value in hexadecimal:
 +"\\23".
 +
 +.RS 0
 +The application does not have to keep the string around after setting this
 +option.
 +.SH ENCODING
 +The string pointed to in the \fICURLOPT_URL(3)\fP argument is generally
 +expected to be a sequence of characters using an ASCII compatible encoding.
 +
 +If libcurl is built with IDN support, the server name part of the URL can use
 +an "international name" by using the current encoding (according to locale) or
 +UTF-8 (when winidn is used).
 +
 +If libcurl is built without IDN support, the server name is used exactly as
 +specified when passed to the name resolver functions.
 +.SH DEFAULT
 +There is no default URL. If this option isn't set, no transfer can be
 +performed.
 +.SH SECURITY CONCERNS
 +Applications may at times find it convenient to allow users to specify URLs
 +for various purposes and that string would then end up fed to this option.
 +
 +Getting a URL from an external untrusted party will bring reasons for several
 +security concerns:
 +
 +If you have an application that runs as or in a server application, getting an
 +unfiltered URL can easily trick your application to access a local resource
 +instead of a remote. Protecting yourself against localhost accesses is very
 +hard when accepting user provided URLs.
 +
 +Such custom URLs can also access other ports than you planned as port numbers
 +are part of the regular URL format. The combination of a local host and a
 +custom port number can allow external users to play tricks with your local
 +services.
 +
 +Accepting external URLs may also use other protocols than http:// or other
 +common ones. Restrict what accept with \fICURLOPT_PROTOCOLS(3)\fP.
 +
 +User provided URLs can also be made to point to sites that redirect further on
 +(possibly to other protocols too). Consider your
 +\fICURLOPT_FOLLOWLOCATION(3)\fP and \fICURLOPT_REDIR_PROTOCOLS(3)\fP settings.
 +.SH PROTOCOLS
 +All
 +.SH EXAMPLE
 +.nf
 +CURL *curl = curl_easy_init();
 +if(curl) {
 +  curl_easy_setopt(curl, CURLOPT_URL, "http://example.com";);
 +
 +  curl_easy_perform(curl);
 +}
 +.fi
 +.SH AVAILABILITY
 +POP3 and SMTP were added in 7.31.0
 +.SH RETURN VALUE
 +Returns CURLE_OK on success or CURLE_OUT_OF_MEMORY if there was insufficient
 +heap space.
 +
 +Note that \fIcurl_easy_setopt(3)\fP won't actually parse the given string so
 +given a bad URL, it will not be detected until \fIcurl_easy_perform(3)\fP or
 +similar is called.
 +.SH "SEE ALSO"
 +.BR CURLOPT_VERBOSE "(3), " CURLOPT_PROTOCOLS "(3), "
 +.BR CURLOPT_FORBID_REUSE "(3), " CURLOPT_FRESH_CONNECT "(3), "
 +.BR curl_easy_perform "(3), "
 +.BR CURLINFO_REDIRECT_URL "(3), " CURLOPT_PATH_AS_IS "(3), " CURLOPT_CURLU 
"(3), "

-- 
To stop receiving notification emails like this one, please contact
address@hidden.