Class HTTPHeaderMatch

  • All Implemented Interfaces:
    io.fabric8.kubernetes.api.builder.Editable<HTTPHeaderMatchBuilder>, io.fabric8.kubernetes.api.model.KubernetesResource, Serializable

    @Generated("io.fabric8.kubernetes.schema.generator.model.ModelGenerator")
    public class HTTPHeaderMatch
    extends Object
    implements io.fabric8.kubernetes.api.builder.Editable<HTTPHeaderMatchBuilder>, io.fabric8.kubernetes.api.model.KubernetesResource
    HTTPHeaderMatch describes how to select a HTTP route by matching HTTP request headers.
    See Also:
    Serialized Form
    • Constructor Detail

      • HTTPHeaderMatch

        public HTTPHeaderMatch()
        No args constructor for use in serialization
    • Method Detail

      • getName

        public String getName()
        Name is the name of the HTTP Header to be matched. Name matching MUST be case insensitive. (See https://tools.ietf.org/html/rfc7230#section-3.2).


        If multiple entries specify equivalent header names, only the first entry with an equivalent name MUST be considered for a match. Subsequent entries with an equivalent header name MUST be ignored. Due to the case-insensitivity of header names, "foo" and "Foo" are considered equivalent.


        When a header is repeated in an HTTP request, it is implementation-specific behavior as to how this is represented. Generally, proxies should follow the guidance from the RFC: https://www.rfc-editor.org/rfc/rfc7230.html#section-3.2.2 regarding processing a repeated header, with special handling for "Set-Cookie".

      • setName

        public void setName​(String name)
        Name is the name of the HTTP Header to be matched. Name matching MUST be case insensitive. (See https://tools.ietf.org/html/rfc7230#section-3.2).


        If multiple entries specify equivalent header names, only the first entry with an equivalent name MUST be considered for a match. Subsequent entries with an equivalent header name MUST be ignored. Due to the case-insensitivity of header names, "foo" and "Foo" are considered equivalent.


        When a header is repeated in an HTTP request, it is implementation-specific behavior as to how this is represented. Generally, proxies should follow the guidance from the RFC: https://www.rfc-editor.org/rfc/rfc7230.html#section-3.2.2 regarding processing a repeated header, with special handling for "Set-Cookie".

      • getType

        public String getType()
        Type specifies how to match against the value of the header.


        Support: Core (Exact)


        Support: Implementation-specific (RegularExpression)


        Since RegularExpression HeaderMatchType has implementation-specific conformance, implementations can support POSIX, PCRE or any other dialects of regular expressions. Please read the implementation's documentation to determine the supported dialect.

      • setType

        public void setType​(String type)
        Type specifies how to match against the value of the header.


        Support: Core (Exact)


        Support: Implementation-specific (RegularExpression)


        Since RegularExpression HeaderMatchType has implementation-specific conformance, implementations can support POSIX, PCRE or any other dialects of regular expressions. Please read the implementation's documentation to determine the supported dialect.

      • getValue

        public String getValue()
        Value is the value of HTTP Header to be matched.
      • setValue

        public void setValue​(String value)
        Value is the value of HTTP Header to be matched.
      • getAdditionalProperties

        public Map<String,​Object> getAdditionalProperties()
      • setAdditionalProperty

        public void setAdditionalProperty​(String name,
                                          Object value)
      • setAdditionalProperties

        public void setAdditionalProperties​(Map<String,​Object> additionalProperties)