External Processing Filter

This extension has the qualified name envoy.filters.http.ext_proc

Note

This extension is functional but has not had substantial production burn time, use only with this caveat.

This extension has an unknown security posture and should only be used in deployments where both the downstream and upstream are trusted.

Tip

This extension extends and can be used with the following extension category:

This extension must be configured with one of the following type URLs:

Warning

This API feature is currently work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.

External Processing Filter Processing Mode

This configuration describes which parts of an HTTP request and response are sent to a remote server and how they are delivered.

extensions.filters.http.ext_proc.v3.ProcessingMode

[extensions.filters.http.ext_proc.v3.ProcessingMode proto]

{
  "request_header_mode": "...",
  "response_header_mode": "...",
  "request_body_mode": "...",
  "response_body_mode": "...",
  "request_trailer_mode": "...",
  "response_trailer_mode": "..."
}
request_header_mode

(extensions.filters.http.ext_proc.v3.ProcessingMode.HeaderSendMode) How to handle the request header. Default is “SEND”.

response_header_mode

(extensions.filters.http.ext_proc.v3.ProcessingMode.HeaderSendMode) How to handle the response header. Default is “SEND”.

request_body_mode

(extensions.filters.http.ext_proc.v3.ProcessingMode.BodySendMode) How to handle the request body. Default is “NONE”.

response_body_mode

(extensions.filters.http.ext_proc.v3.ProcessingMode.BodySendMode) How do handle the response body. Default is “NONE”.

request_trailer_mode

(extensions.filters.http.ext_proc.v3.ProcessingMode.HeaderSendMode) How to handle the request trailers. Default is “SKIP”.

response_trailer_mode

(extensions.filters.http.ext_proc.v3.ProcessingMode.HeaderSendMode) How to handle the response trailers. Default is “SKIP”.

Enum extensions.filters.http.ext_proc.v3.ProcessingMode.HeaderSendMode

[extensions.filters.http.ext_proc.v3.ProcessingMode.HeaderSendMode proto]

Control how headers and trailers are handled

DEFAULT

(DEFAULT) ⁣The default HeaderSendMode depends on which part of the message is being processed. By default, request and response headers are sent, while trailers are skipped.

SEND

⁣Send the header or trailer.

SKIP

⁣Do not send the header or trailer.

Enum extensions.filters.http.ext_proc.v3.ProcessingMode.BodySendMode

[extensions.filters.http.ext_proc.v3.ProcessingMode.BodySendMode proto]

Control how the request and response bodies are handled

NONE

(DEFAULT) ⁣Do not send the body at all. This is the default.

STREAMED

⁣Stream the body to the server in pieces as they arrive at the proxy.

BUFFERED

⁣Buffer the message body in memory and send the entire body at once. If the body exceeds the configured buffer limit, then the downstream system will receive an error.

BUFFERED_PARTIAL

⁣Buffer the message body in memory and send the entire body in one chunk. If the body exceeds the configured buffer limit, then the body contents up to the buffer limit will be sent.