2016-11-16 16:20:36 +03:00
|
|
|
Long: connect-to
|
|
|
|
|
Arg: <HOST1:PORT1:HOST2:PORT2>
|
|
|
|
|
Help: Connect to host
|
|
|
|
|
Added: 7.49.0
|
|
|
|
|
See-also: resolve header
|
2020-07-13 15:15:04 +03:00
|
|
|
Category: connection
|
2021-08-31 17:37:14 +03:00
|
|
|
Example: --connect-to example.com:443:example.net:8443 $URL
|
2016-11-16 16:20:36 +03:00
|
|
|
---
|
|
|
|
|
|
2017-08-12 18:32:33 +03:00
|
|
|
For a request to the given HOST1:PORT1 pair, connect to HOST2:PORT2 instead.
|
|
|
|
|
This option is suitable to direct requests at a specific server, e.g. at a
|
|
|
|
|
specific cluster node in a cluster of servers. This option is only used to
|
|
|
|
|
establish the network connection. It does NOT affect the hostname/port that is
|
|
|
|
|
used for TLS/SSL (e.g. SNI, certificate verification) or for the application
|
|
|
|
|
protocols. "HOST1" and "PORT1" may be the empty string, meaning "any
|
|
|
|
|
host/port". "HOST2" and "PORT2" may also be the empty string, meaning "use the
|
|
|
|
|
request's original host/port".
|
|
|
|
|
|
2017-08-12 18:36:12 +03:00
|
|
|
A "host" specified to this option is compared as a string, so it needs to
|
|
|
|
|
match the name used in request URL. It can be either numerical such as
|
2017-08-12 18:32:33 +03:00
|
|
|
"127.0.0.1" or the full host name such as "example.org".
|
2016-11-16 16:20:36 +03:00
|
|
|
|
|
|
|
|
This option can be used many times to add many connect rules.
|
