Lines Matching +full:whatwg +full:- +full:encoding

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
28 interpretations and the moving nature of the WHATWG spec does however make it
68 inter-operate better with URLs that appear in the wild.
77 is a violation of RFC 3986 but is fine in the WHATWG spec. curl handles these
78 by re-encoding them to `%20`.
80 ### non-ASCII
83 are percent-encoded by curl.
89 RFC 3986 but not according to the WHATWG spec - which allows one to infinity
95 ### "scheme-less"
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
118 They are however not reserved or special in the WHATWG specification, so
120 (using `--globoff`).
124 A URL may consist of the following components - many of them are optional:
186 This is done to make sure the host accessed is truly the localhost - the local
192 handle hostnames using non-ASCII characters.
195 to the WHATWG URL spec, but differs from certain browsers that use IDNA 2003
206 number to use. 1 - 65535. curl also supports a blank port number field - but
241 ### Windows-specific FILE details
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\""
389 traditional URL, followed by a space and a series of space-separated