From 3f25e63df0f63c5eddfbdd0df3d92a515bd358a3 Mon Sep 17 00:00:00 2001 From: Alyssa Wilk Date: Thu, 25 Jan 2018 16:32:00 -0500 Subject: [PATCH] Adding configuration for 100-continue Signed-off-by: Alyssa Wilk --- api/filter/network/http_connection_manager.proto | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/api/filter/network/http_connection_manager.proto b/api/filter/network/http_connection_manager.proto index fc5e487d1..13d158b7d 100644 --- a/api/filter/network/http_connection_manager.proto +++ b/api/filter/network/http_connection_manager.proto @@ -183,6 +183,13 @@ message HttpConnectionManager { // :ref:`config_http_conn_man_headers_x-forwarded-client-cert` header, *Hash* is always set, and // *By* is always set when the client certificate presents the SAN value. SetCurrentClientCertDetails set_current_client_cert_details = 17; + + // [#not-implemented-hide:] + // If proxy_100_continue is true, Envoy will proxy incoming "Expect: + // 100-continue" headers upstream, and forward "100 Continue" responses + // downstream. If this is false or not set, Envoy will instead strip the + // "Expect: 100-continue" header, and send a "100 Continue" response itself. + bool proxy_100_continue = 18; } message Rds {