Class HttpHeaderMatch (1.3.1)

Version 1.3.1

• 1.22.0 (latest)
• 1.21.0
• 1.20.1
• 1.19.2
• 1.18.0
• 1.17.0
• 1.16.1
• 1.15.0
• 1.14.1
• 1.13.0
• 1.12.1
• 1.11.0
• 1.10.1
• 1.9.0
• 1.8.0
• 1.7.0
• 1.6.1
• 1.5.2
• 1.4.0
• 1.3.2
• 1.2.0
• 1.1.0
• 1.0.0
• 0.9.0
• 0.8.0
• 0.7.0
• 0.6.0
• 0.5.0
• 0.4.2
• 0.3.0
• 0.2.1
• 0.1.0

HttpHeaderMatch(mapping=None, *, ignore_unknown_fields=False, **kwargs)

matchRule criteria for request header matches.

Attributes

Name	Description
exact_match	str The value should exactly match contents of exactMatch. Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch must be set. This field is a member of `oneof`_ ``_exact_match``.
header_name	str The name of the HTTP header to match. For matching against the HTTP request's authority, use a headerMatch with the header name ":authority". For matching a request's method, use the headerName ":method". When the URL map is bound to a target gRPC proxy that has the validateForProxyless field set to true, only non-binary user-specified custom metadata and the ``content-type`` header are supported. The following transport-level headers cannot be used in header matching rules: ``:authority``, ``:method``, ``:path``, ``:scheme``, ``user-agent``, ``accept-encoding``, ``content-encoding``, ``grpc-accept-encoding``, ``grpc-encoding``, ``grpc-previous-rpc-attempts``, ``grpc-tags-bin``, ``grpc-timeout`` and ``grpc-trace-bin``. This field is a member of `oneof`_ ``_header_name``.
invert_match	bool If set to false, the headerMatch is considered a match if the preceding match criteria are met. If set to true, the headerMatch is considered a match if the preceding match criteria are NOT met. The default setting is false. This field is a member of `oneof`_ ``_invert_match``.
prefix_match	str The value of the header must start with the contents of prefixMatch. Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch must be set. This field is a member of `oneof`_ ``_prefix_match``.
present_match	bool A header with the contents of headerName must exist. The match takes place whether or not the request's header has a value. Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch must be set. This field is a member of `oneof`_ ``_present_match``.
range_match	google.cloud.compute_v1.types.Int64RangeMatch The header value must be an integer and its value must be in the range specified in rangeMatch. If the header does not contain an integer, number or is empty, the match fails. For example for a range [-5, 0] - -3 will match. - 0 will not match. - 0.25 will not match. - -3someString will not match. Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch must be set. rangeMatch is not supported for load balancers that have loadBalancingScheme set to EXTERNAL. This field is a member of `oneof`_ ``_range_match``.
regex_match	str The value of the header must match the regular expression specified in regexMatch. For more information about regular expression syntax, see Syntax. For matching against a port specified in the HTTP request, use a headerMatch with headerName set to PORT and a regular expression that satisfies the RFC2616 Host header's port specifier. Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch must be set. regexMatch only applies to load balancers that have loadBalancingScheme set to INTERNAL_SELF_MANAGED. This field is a member of `oneof`_ ``_regex_match``.
suffix_match	str The value of the header must end with the contents of suffixMatch. Only one of exactMatch, prefixMatch, suffixMatch, regexMatch, presentMatch or rangeMatch must be set. This field is a member of `oneof`_ ``_suffix_match``.

Inheritance

builtins.object > proto.message.Message > HttpHeaderMatch