| xf.li | 6c8fc1e | 2023-08-12 00:11:09 -0700 | [diff] [blame^] | 1 | c: Copyright (C) 1998 - 2022, Daniel Stenberg, <daniel@haxx.se>, et al. |
| 2 | SPDX-License-Identifier: curl |
| 3 | Long: socks4 |
| 4 | Arg: <host[:port]> |
| 5 | Help: SOCKS4 proxy on given host + port |
| 6 | Added: 7.15.2 |
| 7 | Category: proxy |
| 8 | Example: --socks4 hostname:4096 $URL |
| 9 | See-also: socks4a socks5 socks5-hostname |
| 10 | Multi: single |
| 11 | --- |
| 12 | Use the specified SOCKS4 proxy. If the port number is not specified, it is |
| 13 | assumed at port 1080. Using this socket type make curl resolve the host name |
| 14 | and passing the address on to the proxy. |
| 15 | |
| 16 | To specify proxy on a unix domain socket, use localhost for host, e.g. |
| 17 | socks4://localhost/path/to/socket.sock |
| 18 | |
| 19 | This option overrides any previous use of --proxy, as they are mutually |
| 20 | exclusive. |
| 21 | |
| 22 | This option is superfluous since you can specify a socks4 proxy with --proxy |
| 23 | using a socks4:// protocol prefix. (Added in 7.21.7) |
| 24 | |
| 25 | Since 7.52.0, --preproxy can be used to specify a SOCKS proxy at the same time |
| 26 | --proxy is used with an HTTP/HTTPS proxy. In such a case curl first connects to |
| 27 | the SOCKS proxy and then connects (through SOCKS) to the HTTP or HTTPS proxy. |