Lines Matching +full:- +full:- +full:disable +full:- +full:ldap

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/)
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.
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
120 (using `--globoff`).
124 A URL may consist of the following components - many of them are optional:
144 `imaps`, `ldap`, `ldaps`, `mqtt`, `pop3`, `pop3s`, `rtmp`, `rtmpe`, `rtmps`,
186 This is done to make sure the host accessed is truly the localhost - the local
192 handle hostnames using non-ASCII characters.
206 number to use. 1 - 65535. curl also supports a blank port number field - but
213 IMAP 132, IMAPS 993, LDAP 369, LDAPS 636, MQTT 1883, POP3 110, POP3S 995,
241 ### Windows-specific FILE details
250 cannot control or disable.
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\""
318 ## LDAP
320 The path part of a LDAP request can be used to specify the: Distinguished
321 Name, Attributes, Scope, Filter and Extension for a LDAP search. Each field is
327     ldap://ldap.example.com/o=My%20Organization
331     ldap://ldap.example.com/o=My%20Organization?postalAddress
336     ldap://ldap.example.com/?rootDomainNamingContext
338 For more information about the individual components of a LDAP URL please
389 traditional URL, followed by a space and a series of space-separated