hosts
Parameters
The list of host patterns to match. Host patterns must be valid hostnames. Ports are not allowed. Wildcard hosts are supported in the suffix or prefix form. * matches any string of (a-z0-9-.*). It does not match the empty string. When multiple hosts are specified, hosts are matched in the following priority:
Exact domain names:
`www.foo.com`
.Suffix domain wildcards:
`*.foo.com`
or`*-bar.foo.com`
.Prefix domain wildcards:
`foo.*`
or`foo-*`
.Special wildcard
`*`
matching any domain. Notes: The wildcard will not match the empty string. e.g.`*-bar.foo.com`
will match`baz-bar.foo.com`
but not`-bar.foo.com`
. The longest wildcards match first. Only a single host in the entire service can match on`*`
. A domain must be unique across all configured hosts within a service. Hosts are matched against the HTTP Host header, or for HTTP/2 and HTTP/3, the ":authority" header, from the incoming request. You may specify up to 10 hosts.
Parameters
The list of host patterns to match. Host patterns must be valid hostnames. Ports are not allowed. Wildcard hosts are supported in the suffix or prefix form. * matches any string of (a-z0-9-.*). It does not match the empty string. When multiple hosts are specified, hosts are matched in the following priority:
Exact domain names:
`www.foo.com`
.Suffix domain wildcards:
`*.foo.com`
or`*-bar.foo.com`
.Prefix domain wildcards:
`foo.*`
or`foo-*`
.Special wildcard
`*`
matching any domain. Notes: The wildcard will not match the empty string. e.g.`*-bar.foo.com`
will match`baz-bar.foo.com`
but not`-bar.foo.com`
. The longest wildcards match first. Only a single host in the entire service can match on`*`
. A domain must be unique across all configured hosts within a service. Hosts are matched against the HTTP Host header, or for HTTP/2 and HTTP/3, the ":authority" header, from the incoming request. You may specify up to 10 hosts.