2016-11-28 07:50:25 +08:00
|
|
|
Long: socks4a
|
|
|
|
Arg: <host[:port]>
|
|
|
|
Help: SOCKS4a proxy on given host + port
|
|
|
|
Added: 7.18.0
|
2020-07-13 20:15:04 +08:00
|
|
|
Category: proxy
|
2021-08-31 22:37:14 +08:00
|
|
|
Example: --socks4a hostname:4096 $URL
|
2016-11-28 07:50:25 +08:00
|
|
|
---
|
|
|
|
Use the specified SOCKS4a proxy. If the port number is not specified, it is
|
2021-06-17 23:26:36 +08:00
|
|
|
assumed at port 1080. This asks the proxy to resolve the host name.
|
2016-11-28 07:50:25 +08:00
|
|
|
|
2017-02-10 07:26:16 +08:00
|
|
|
This option overrides any previous use of --proxy, as they are mutually
|
|
|
|
exclusive.
|
|
|
|
|
2021-09-28 16:30:59 +08:00
|
|
|
This option is superfluous since you can specify a socks4a proxy with --proxy
|
|
|
|
using a socks4a:// protocol prefix. (Added in 7.21.7)
|
2016-11-28 07:50:25 +08:00
|
|
|
|
2017-02-10 07:26:16 +08:00
|
|
|
Since 7.52.0, --preproxy can be used to specify a SOCKS proxy at the same time
|
|
|
|
--proxy is used with an HTTP/HTTPS proxy. In such a case curl first connects to
|
2017-02-06 16:13:42 +08:00
|
|
|
the SOCKS proxy and then connects (through SOCKS) to the HTTP or HTTPS proxy.
|
|
|
|
|
2016-11-28 07:50:25 +08:00
|
|
|
If this option is used several times, the last one will be used.
|