consul/test
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
..
bin test: log exit code in cluster.bash 2017-06-08 14:06:10 +02:00
ca Update test certificates that expire this year to be way in the future 2018-05-12 10:15:45 +01:00
ca_path Add tls client options to api/cli 2017-04-14 13:37:29 -07:00
client_certs Adds enable_agent_tls_for_checks configuration option which allows (#3661) 2017-11-07 18:22:09 -08:00
command/merge Add utility types to enable checking for unset flags 2017-02-07 20:14:41 -05:00
hostname wan federation via mesh gateways (#6884) 2020-03-09 15:59:02 -05:00
integration/connect/envoy Always require Host header values for http services (#7990) 2020-06-08 18:16:48 +00:00
key tls: auto_encrypt enables automatic RPC cert provisioning for consul clients (#5597) 2019-06-27 22:22:07 +02:00
snapshot snapshot: read meta.json correctly. (#5193) 2019-01-08 17:06:28 +01:00
notes.txt Adding testing certificates 2014-04-07 15:07:00 -07:00