consul/test/integration/connect/envoy/case-ingress-gateway-http
Chris Piraino 165a9af053 Always require Host header values for http services (#7990)
Previously, we did not require the 'service-name.*' host header value
when on a single http service was exposed. However, this allows a user
to get into a situation where, if they add another service to the
listener, suddenly the previous service's traffic might not be routed
correctly. Thus, we always require the Host header, even if there is
only 1 service.

Also, we add the make the default domain matching more restrictive by
matching "service-name.ingress.*" by default. This lines up better with
the namespace case and more accurately matches the Consul DNS value we
expect people to use in this case.
2020-06-08 18:16:48 +00:00
..
capture.sh Add http routing support and integration test to ingress gateways 2020-04-24 09:31:32 -05:00
config_entries.hcl Require individual services in ingress entry to match protocols (#7774) 2020-05-06 16:09:24 -05:00
gateway.hcl Add http routing support and integration test to ingress gateways 2020-04-24 09:31:32 -05:00
setup.sh Add http routing support and integration test to ingress gateways 2020-04-24 09:31:32 -05:00
vars.sh Add http routing support and integration test to ingress gateways 2020-04-24 09:31:32 -05:00
verify.bats Always require Host header values for http services (#7990) 2020-06-08 18:16:48 +00:00