Common HTTP Inputs (proto)

type.matcher.v3.HttpResponseStatusCodeMatchInput

[type.matcher.v3.HttpResponseStatusCodeMatchInput proto]

Match input indicates that matching should be done on the response status code.

type.matcher.v3.HttpResponseStatusCodeClassMatchInput

[type.matcher.v3.HttpResponseStatusCodeClassMatchInput proto]

Match input indicates that the matching should be done on the class of the response status code. For eg: 1xx, 2xx, 3xx, 4xx or 5xx.

type.matcher.v3.HttpResponseLocalReplyMatchInput

[type.matcher.v3.HttpResponseLocalReplyMatchInput proto]

This match input determines whether the response is a local reply which gets generated by Envoy or a response from the upstream.

The input string is true for local replies and false for the upstream responses.

It can be used with the custom_response filter to apply policies only to the Envoy generated local replies.

This extension has the qualified name envoy.matching.inputs.local_reply

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: