Common HTTP Inputs

type.matcher.v3.HttpRequestHeaderMatchInput

[type.matcher.v3.HttpRequestHeaderMatchInput proto]

Match input indicates that matching should be done on a specific request header. The resulting input string will be all headers for the given key joined by a comma, e.g. if the request contains two ‘foo’ headers with value ‘bar’ and ‘baz’, the input string will be ‘bar,baz’.

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

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:

{
  "header_name": "..."
}
header_name

(string) The request header to match on.

type.matcher.v3.HttpRequestTrailerMatchInput

[type.matcher.v3.HttpRequestTrailerMatchInput proto]

Match input indicates that matching should be done on a specific request trailer. The resulting input string will be all headers for the given key joined by a comma, e.g. if the request contains two ‘foo’ headers with value ‘bar’ and ‘baz’, the input string will be ‘bar,baz’.

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

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:

{
  "header_name": "..."
}
header_name

(string) The request trailer to match on.

type.matcher.v3.HttpResponseHeaderMatchInput

[type.matcher.v3.HttpResponseHeaderMatchInput proto]

Match input indicating that matching should be done on a specific response header. The resulting input string will be all headers for the given key joined by a comma, e.g. if the response contains two ‘foo’ headers with value ‘bar’ and ‘baz’, the input string will be ‘bar,baz’.

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

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:

{
  "header_name": "..."
}
header_name

(string) The response header to match on.

type.matcher.v3.HttpResponseTrailerMatchInput

[type.matcher.v3.HttpResponseTrailerMatchInput proto]

Match input indicates that matching should be done on a specific response trailer. The resulting input string will be all headers for the given key joined by a comma, e.g. if the request contains two ‘foo’ headers with value ‘bar’ and ‘baz’, the input string will be ‘bar,baz’.

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

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:

{
  "header_name": "..."
}
header_name

(string) The response trailer to match on.