Composite

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

Note

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:

Composite Filter configuration overview.

extensions.filters.http.composite.v3.Composite

[extensions.filters.http.composite.v3.Composite proto]

Composite filter config. The composite filter config allows delegating filter handling to another filter as determined by matching on the request headers. This makes it possible to use different filters or filter configurations based on the incoming request.

This is intended to be used with ExtensionWithMatcher where a match tree is specified that indicates (via ExecuteFilterAction) which filter configuration to create and delegate to.

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.

extensions.filters.http.composite.v3.ExecuteFilterAction

[extensions.filters.http.composite.v3.ExecuteFilterAction proto]

Composite match action (see matching docs for more info on match actions). This specifies the filter configuration of the filter that the composite filter should delegate filter interactions to.

{
  "typed_config": "{...}"
}
typed_config

(config.core.v3.TypedExtensionConfig)