mirror of
https://github.com/curl/curl.git
synced 2024-12-27 06:59:43 +08:00
37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
---
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: socks4
|
|
Arg: <host[:port]>
|
|
Help: SOCKS4 proxy on given host + port
|
|
Added: 7.15.2
|
|
Category: proxy
|
|
Multi: single
|
|
See-also:
|
|
- socks4a
|
|
- socks5
|
|
- socks5-hostname
|
|
Example:
|
|
- --socks4 hostname:4096 $URL
|
|
---
|
|
|
|
# `--socks4`
|
|
|
|
Use the specified SOCKS4 proxy. If the port number is not specified, it is
|
|
assumed at port 1080. Using this socket type make curl resolve the hostname
|
|
and passing the address on to the proxy.
|
|
|
|
To specify proxy on a unix domain socket, use localhost for host, e.g.
|
|
`socks4://localhost/path/to/socket.sock`
|
|
|
|
This option overrides any previous use of --proxy, as they are mutually
|
|
exclusive.
|
|
|
|
This option is superfluous since you can specify a socks4 proxy with --proxy
|
|
using a socks4:// 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.
|