From 2487368848035a1afc202c3ec8d60a66d56e190f Mon Sep 17 00:00:00 2001 From: Raven Black Date: Fri, 17 Jan 2025 13:43:25 -0500 Subject: [PATCH] Remove incorrect/outdated doc for explicit_http_config (#38090) Commit Message: Remove incorrect/outdated doc for explicit_http_config Additional Description: Per #38064, this docstring became incorrect with #14362 so should be removed. Risk Level: None, doc-only. Testing: n/a Docs Changes: Yes it is. Release Notes: n/a Platform Specific Features: n/a Signed-off-by: Raven Black Signed-off-by: Sheldon --- .../extensions/upstreams/http/v3/http_protocol_options.proto | 1 - 1 file changed, 1 deletion(-) diff --git a/api/envoy/extensions/upstreams/http/v3/http_protocol_options.proto b/api/envoy/extensions/upstreams/http/v3/http_protocol_options.proto index ca4cb81fe033..7e3ed435edd3 100644 --- a/api/envoy/extensions/upstreams/http/v3/http_protocol_options.proto +++ b/api/envoy/extensions/upstreams/http/v3/http_protocol_options.proto @@ -140,7 +140,6 @@ message HttpProtocolOptions { option (validate.required) = true; // To explicitly configure either HTTP/1 or HTTP/2 (but not both!) use ``explicit_http_config``. - // If the ``explicit_http_config`` is empty, HTTP/1.1 is used. ExplicitHttpConfig explicit_http_config = 3; // This allows switching on protocol based on what protocol the downstream