Lines Matching +full:- +full:- +full:with +full:- +full:librtmp

1 <!--
4 SPDX-License-Identifier: curl
5 -->
14  - [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986) (although URL is called
16  - [The WHATWG URL Specification](https://url.spec.whatwg.org/)
21 The WHATWG URL spec was written later, is incompatible with the RFC 3986 and
46 URL from an external untrusted party and using it with curl brings several
56    custom port number can allow external users to play tricks with your local
68 inter-operate better with URLs that appear in the wild.
78 by re-encoding them to `%20`.
80 ### Non-ASCII
83 are percent-encoded by curl.
87 An absolute URL always starts with a "scheme" followed by a colon. For all the
89 RFC 3986 but not according to the WHATWG spec - which allows one to infinity
95 ### "scheme-less"
97 curl supports "URLs" that do not start with a scheme. This is not supported by
101 Based on what the hostname starts with, curl "guesses" what protocol to use:
103  - `ftp.` means FTP
104  - `dict.` means DICT
105  - `ldap.` means LDAP
106  - `imap.` means IMAP
107  - `smtp.` means SMTP
108  - `pop3.` means POP3
109  - all other means HTTP
114 create ranges and lists using `[N-M]` and `{one,two,three}` sequences. The
120 (using `--globoff`).
124 A URL may consist of the following components - many of them are optional:
128 Each component is separated from the following component with a divider
186 This is done to make sure the host accessed is truly the localhost - the local
191 If curl was built with International Domain Name (IDN) support, it can also
192 handle hostnames using non-ASCII characters.
194 When built with libidn2, curl uses the IDNA 2008 standard. This is equivalent
197 slightly, perhaps most famously in how they deal with the German "double s"
206 number to use. 1 - 65535. curl also supports a blank port number field - but
207 only if the URL starts with a scheme.
228 server, start the path with double slash `//` or `/%2f` (2F is the hexadecimal
241 ### Windows-specific FILE details
243 curl accepts that the FILE URL's path starts with a "drive letter". That is a
267 Select the user's inbox and fetch message with `uid = 1`:
300 numbers (`UID`) by using a custom curl request via `-X`. `UID` numbers are
309     imap://user:password@mail.example.com/INBOX -X "UID SEARCH TEXT \"foo bar\""
323 string with the question mark separator should be included.
358 path ends with a slash (`/`) then a directory listing is returned instead of a
376 communication with the mail server. If the path is omitted, then libcurl
388 by the underlying librtmp library. It has a syntax where it wants a
389 traditional URL, followed by a space and a series of space-separated