620401f193
After Gmail called out the typo I fixed on
532d89a866, I've decided to paste the
whole man page into Google docs and check what other issues it would
spot.
I know, it sounds silly, but I've just spent the last hour and a half
going over each one of them and fixing everything which was a true
finding and non-controversial.
Closes #17480
1.3 KiB
| c | SPDX-License-Identifier | Long | Arg | Help | Added | Category | Multi | See-also | Example | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al. | curl | connect-to | <HOST1:PORT1:HOST2:PORT2> | Connect to host2 instead of host1 | 7.49.0 | connection dns | append |
|
|
--connect-to
For a request intended for the HOST1:PORT1 pair, connect to HOST2:PORT2
instead. This option is only used to establish the network connection. It does
NOT affect the hostname/port number that is used for TLS/SSL (e.g. SNI,
certificate verification) or for the application protocols.
HOST1 and PORT1 may be empty strings, meaning any host or any port number.
HOST2 and PORT2 may also be empty strings, meaning use the request's
original hostname and port number.
A hostname specified to this option is compared as a string, so it needs to
match the name used in the request URL. It can be either numerical such as
127.0.0.1 or the full host name such as example.org.
Example: redirect connects from the example.com hostname to 127.0.0.1 independently of port number:
curl --connect-to example.com::127.0.0.1: https://example.com/
Example: redirect connects from all hostnames to 127.0.0.1 independently of port number:
curl --connect-to ::127.0.0.1: http://example.com/