Uses of Package
io.envoyproxy.envoy.extensions.filters.http.ext_proc.v3
Packages that use io.envoyproxy.envoy.extensions.filters.http.ext_proc.v3
Package
Description
-
Classes in io.envoyproxy.envoy.extensions.filters.http.ext_proc.v3 used by io.envoyproxy.envoy.extensions.filters.http.ext_proc.v3ClassDescriptionThe filter communicates with an external gRPC service called an "external processor" that can do a variety of things with the request and response: * Access and modify the HTTP headers on the request, response, or bothThe filter communicates with an external gRPC service called an "external processor" that can do a variety of things with the request and response: * Access and modify the HTTP headers on the request, response, or bothDescribes the route cache action to be taken when an external processor response is received in response to request headers.ExtProcHttpService is used for HTTP communication between the filter and the external processing service.ExtProcHttpService is used for HTTP communication between the filter and the external processing service.Overrides that may be set on a per-route basis [#next-free-field: 10]Overrides that may be set on a per-route basis [#next-free-field: 10]Extra settings that may be added to per-route configuration for a virtual host or cluster.Extra settings that may be added to per-route configuration for a virtual host or cluster.The HeaderForwardingRules structure specifies what headers are allowed to be forwarded to the external processing server.The HeaderForwardingRules structure specifies what headers are allowed to be forwarded to the external processing server.The MetadataOptions structure defines options for the sending and receiving of dynamic metadata.The MetadataOptions structure defines options for the sending and receiving of dynamic metadata.Protobuf type
envoy.extensions.filters.http.ext_proc.v3.MetadataOptions.MetadataNamespacesProtobuf typeenvoy.extensions.filters.http.ext_proc.v3.MetadataOptions.MetadataNamespaces[#next-free-field: 7]Control how the request and response bodies are handled When body mutation by external processor is enabled, ext_proc filter will always remove the content length header in four cases below because content length can not be guaranteed to be set correctly: 1) STREAMED BodySendMode: header processing completes before body mutation comes back. 2) BUFFERED_PARTIAL BodySendMode: body is buffered and could be injected in different phases. 3) BUFFERED BodySendMode + SKIP HeaderSendMode: header processing (e.g., update content-length) is skipped. 4) FULL_DUPLEX_STREAMED BodySendMode: header processing completes before body mutation comes back.[#next-free-field: 7]Control how headers and trailers are handled -
Classes in io.envoyproxy.envoy.extensions.filters.http.ext_proc.v3 used by io.envoyproxy.envoy.service.ext_proc.v3ClassDescription[#next-free-field: 7]Control how the request and response bodies are handled When body mutation by external processor is enabled, ext_proc filter will always remove the content length header in four cases below because content length can not be guaranteed to be set correctly: 1) STREAMED BodySendMode: header processing completes before body mutation comes back. 2) BUFFERED_PARTIAL BodySendMode: body is buffered and could be injected in different phases. 3) BUFFERED BodySendMode + SKIP HeaderSendMode: header processing (e.g., update content-length) is skipped. 4) FULL_DUPLEX_STREAMED BodySendMode: header processing completes before body mutation comes back.[#next-free-field: 7]