From 047f2887f2196ce321eeceed768e173dff95ca72 Mon Sep 17 00:00:00 2001
From: "update-envoy[bot]"
 <135279899+update-envoy[bot]@users.noreply.github.com>
Date: Fri, 6 Sep 2024 17:37:29 +0000
Subject: [PATCH] Mirrored from envoyproxy/envoy @
 1130fca31d99f9c7ceff7fd0a1d2c4ee8ca25064

Signed-off-by: update-envoy[bot] <135279899+update-envoy[bot]@users.noreply.github.com>
---
 envoy/COMMIT                                  |  2 +-
 .../v3/upstream_http_11_connect.pb.go         | 36 ++++++++-----------
 2 files changed, 15 insertions(+), 23 deletions(-)

diff --git a/envoy/COMMIT b/envoy/COMMIT
index 1ce3607689..d42a91d0a4 100644
--- a/envoy/COMMIT
+++ b/envoy/COMMIT
@@ -1 +1 @@
-b7e13f1d806f244da5fef2578e61c1e06a12fb33
+1130fca31d99f9c7ceff7fd0a1d2c4ee8ca25064
diff --git a/envoy/extensions/transport_sockets/http_11_proxy/v3/upstream_http_11_connect.pb.go b/envoy/extensions/transport_sockets/http_11_proxy/v3/upstream_http_11_connect.pb.go
index f8ca4c10cd..daf532a41e 100755
--- a/envoy/extensions/transport_sockets/http_11_proxy/v3/upstream_http_11_connect.pb.go
+++ b/envoy/extensions/transport_sockets/http_11_proxy/v3/upstream_http_11_connect.pb.go
@@ -23,30 +23,22 @@ const (
 	_ = protoimpl.EnforceVersion(protoimpl.MaxVersion - 20)
 )
 
-// The HTTP/1.1 proxy transport socket opens an upstream connection to a specified proxy address
-// rather than the target host's address. If this transport socket is configured and proxy
-// information is configured, then:
+// HTTP/1.1 proxy transport socket establishes an upstream connection to a proxy address
+// instead of the target host's address. This behavior is triggered when the transport
+// socket is configured and proxy information is provided.
 //
-//   - Upstream connections to the proxy address will have a raw HTTP/1.1 CONNECT header prefaced to
-//     the payload, and 200 response stripped (if less than 200 bytes).
-//   - Plaintext HTTP/1.1 connections will be sent with a fully qualified URL.
+// Behavior when proxying:
+// =======================
+// When an upstream connection is established, instead of connecting directly to the endpoint
+// address, the client will connect to the specified proxy address, send an HTTP/1.1 “CONNECT“ request
+// indicating the endpoint address, and process the response. If the response has HTTP status 200,
+// the connection will be passed down to the underlying transport socket.
 //
-// There are two primary ways to configure proxy information:
-//
-//   - An intermediate filter adds the stream info necessary for proxying to the stream info (as the
-//     test filter does :repo:`here <test/integration/filters/header_to_proxy_filter.cc>`).
-//   - Setting the "typed_filter_metadata" in :ref:`LbEndpoint.Metadata <envoy_v3_api_field_config.endpoint.v3.lbendpoint.metadata>`
-//     or :ref:`LocalityLbEndpoints.Metadata
-//     <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>` using the key
-//     "envoy.http11_proxy_transport_socket.proxy_address" and the proxy address in
-//     config::core::v3::Address format.
-//
-// Some important notes regarding this transport socket:
-//
-//   - Configuration via stream info (as opposed to endpoint/locality metadata) will only proxy TLS
-//     connections to the proxy address on port 443. This is to maintain the original behavior of the
-//     transport socket when using this method of configuration.
-//   - The transport socket is not compatible with HTTP/3 or plaintext HTTP/2.
+// Configuring proxy information:
+// ==============================
+// Set “typed_filter_metadata“ in :ref:`LbEndpoint.Metadata <envoy_v3_api_field_config.endpoint.v3.lbendpoint.metadata>` or :ref:`LocalityLbEndpoints.Metadata <envoy_v3_api_field_config.endpoint.v3.LocalityLbEndpoints.metadata>`.
+// using the key “envoy.http11_proxy_transport_socket.proxy_address“ and the
+// proxy address in “config::core::v3::Address“ format.
 type Http11ProxyUpstreamTransport struct {
 	state         protoimpl.MessageState
 	sizeCache     protoimpl.SizeCache