2024-05-15 15:20:32 -04:00
|
|
|
---
|
2023-12-11 20:30:44 -05:00
|
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
|
|
|
SPDX-License-Identifier: curl
|
|
|
|
|
Long: socks5
|
|
|
|
|
Arg: <host[:port]>
|
|
|
|
|
Help: SOCKS5 proxy on given host + port
|
|
|
|
|
Added: 7.18.0
|
|
|
|
|
Category: proxy
|
|
|
|
|
Multi: single
|
2024-05-15 15:20:32 -04:00
|
|
|
See-also:
|
|
|
|
|
- socks5-hostname
|
|
|
|
|
- socks4a
|
|
|
|
|
Example:
|
|
|
|
|
- --socks5 proxy.example:7000 $URL
|
2023-12-11 20:30:44 -05:00
|
|
|
---
|
2024-05-15 15:20:32 -04:00
|
|
|
|
|
|
|
|
# `--socks5`
|
|
|
|
|
|
|
|
|
|
Use the specified SOCKS5 proxy - but resolve the hostname locally. If the
|
2023-12-11 20:30:44 -05:00
|
|
|
port number is not specified, it is assumed at port 1080.
|
|
|
|
|
|
|
|
|
|
To specify proxy on a unix domain socket, use localhost for host, e.g.
|
2024-05-15 15:20:32 -04:00
|
|
|
`socks5://localhost/path/to/socket.sock`
|
2023-12-11 20:30:44 -05:00
|
|
|
|
|
|
|
|
This option overrides any previous use of --proxy, as they are mutually
|
|
|
|
|
exclusive.
|
|
|
|
|
|
|
|
|
|
This option is superfluous since you can specify a socks5 proxy with --proxy
|
|
|
|
|
using a socks5:// 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.
|
|
|
|
|
|
|
|
|
|
This option (as well as --socks4) does not work with IPV6, FTPS or LDAP.
|
