1fb734bc2d
After this patch `://` schemes are lowercase and enclosed in backticks. Also: - docs/libcurl/libcurl-multi.md: drop a stray C code fence. - docs/libcurl/libcurl-tutorial.md: replace single/double quotes with Markdown markup where applicable. Ref: #21646 Closes #21674
1.2 KiB
| c | SPDX-License-Identifier | Long | Arg | Help | Added | Category | Multi | Mutexed | See-also | Example | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al. | curl | socks4a | <host[:port]> | SOCKS4a proxy on given host + port | 7.18.0 | proxy | single | proxy socks4 socks5 socks5-hostname |
|
|
--socks4a
Use the specified SOCKS4a proxy. If the port number is not specified, it is assumed at port 1080. This asks the proxy to resolve the hostname.
To specify the proxy on a Unix domain socket, use localhost for host and
append the absolute path to the domain socket. For example:
socks4a://localhost/path/to/socket.sock (the scheme may be omitted).
This option overrides any previous use of --proxy, as they are mutually exclusive.
This option is superfluous since you can specify a socks4a proxy with --proxy
using a socks4a:// protocol prefix. (Added in 7.21.7)
--preproxy can be used to specify a SOCKS proxy at the same time --proxy is used with an HTTP/HTTPS proxy (added in 7.52.0). In such a case, curl first connects to the SOCKS proxy and then connects (through SOCKS) to the HTTP or HTTPS proxy.