Skip to content

doc: polish http/upgrades documentation #14825

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yanavlasov merged 1 commit into from
Jan 26, 2021
Merged

doc: polish http/upgrades documentation #14825

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/root/intro/arch_overview/http/upgrades.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,11 +117,14 @@ Note that when using HTTP/1 CONNECT you will end up having a TCP connection
between L1 and L2 Envoy for each TCP client connection, it is preferable to use
HTTP/2 when you have the choice.

Examples of such a set up can be found in the Envoy example config :repo:`directory <configs/>`
Examples of such a set up can be found in the Envoy example config :repo:`directory <configs/>`.

For HTTP/1.1 run `bazel-bin/source/exe/envoy-static --config-path configs/encapsulate_in_http1_connect.yaml --base-id 1`
and `bazel-bin/source/exe/envoy-static --config-path configs/terminate_http1_connect.yaml`.

For HTTP/2 run `bazel-bin/source/exe/envoy-static --config-path configs/encapsulate_in_http2_connect.yaml --base-id 1`
and `bazel-bin/source/exe/envoy-static --config-path configs/terminate_http2_connect.yaml`.

In both cases you will be running a first Envoy listening for TCP traffic on port 10000 and encapsulating it in an HTTP
CONNECT request, and a second one listening on 10001, stripping the CONNECT headers, and forwarding the
original TCP upstream, in this case to google.com.
Expand Down