From b76e20bf5da8feb1edd050922454b1fc05f35824 Mon Sep 17 00:00:00 2001 From: "update-envoy[bot]" <135279899+update-envoy[bot]@users.noreply.github.com> Date: Fri, 1 Sep 2023 06:46:28 +0000 Subject: [PATCH] Docs: fixing a few issues in ext_proc documentation (#27851) Signed-off-by: Yanjun Xiang Mirrored from https://github.com/envoyproxy/envoy @ 2ee62ca6ae6cd89fe96e153a641d22fbb8fd4828 --- .../ext_proc/v3/external_processor.proto | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/envoy/service/ext_proc/v3/external_processor.proto b/envoy/service/ext_proc/v3/external_processor.proto index 9d09828e..21ae8c03 100644 --- a/envoy/service/ext_proc/v3/external_processor.proto +++ b/envoy/service/ext_proc/v3/external_processor.proto @@ -170,6 +170,10 @@ message ProcessingResponse { // for the duration of this particular request/response only. Servers // may use this to intelligently control how requests are processed // based on the headers and other metadata that they see. + // This field is ignored by Envoy when the ext_proc filter config + // :ref:`allow_mode_override + // ` + // is set to false. envoy.extensions.filters.http.ext_proc.v3.ProcessingMode mode_override = 9; // When ext_proc server receives a request message, in case it needs more @@ -275,8 +279,11 @@ message CommonResponse { // Replace the body of the last message sent to the remote server on this // stream. If responding to an HttpBody request, simply replace or clear - // the body chunk that was sent with that request. Body mutations only take - // effect in response to ``body`` messages and are ignored otherwise. + // the body chunk that was sent with that request. Body mutations may take + // effect in response either to ``header`` or ``body`` messages. When it is + // in response to ``header`` messages, it only take effect if the + // :ref:`status ` + // is set to CONTINUE_AND_REPLACE. BodyMutation body_mutation = 3; // [#not-implemented-hide:] @@ -285,9 +292,9 @@ message CommonResponse { // along with the CONTINUE_AND_REPLACE status. config.core.v3.HeaderMap trailers = 4; - // Clear the route cache for the current request. - // This is necessary if the remote server - // modified headers that are used to calculate the route. + // Clear the route cache for the current client request. This is necessary + // if the remote server modified headers that are used to calculate the route. + // This field is ignored in the response direction. bool clear_route_cache = 5; }