@@ -37,14 +37,12 @@ pub struct GatewaySpec {
37
37
/// with each other if all of the following conditions are met:
38
38
///
39
39
/// 1. Either each Listener within the group specifies the "HTTP" Protocol or
40
- /// each Listener within the group specifies either the "HTTPS" or "TLS"
41
- /// Protocol.
42
- ///
40
+ /// each Listener within the group specifies either the "HTTPS" or "TLS"
41
+ /// Protocol.
43
42
/// 2. Each Listener within the group specifies a Hostname that is unique
44
- /// within the group.
45
- ///
43
+ /// within the group.
46
44
/// 3. As a special case, one Listener within a group may omit Hostname, in
47
- /// which case this Listener matches when no other Listener matches.
45
+ /// which case this Listener matches when no other Listener matches.
48
46
///
49
47
/// If the implementation does collapse compatible Listeners, the hostname
50
48
/// provided in the incoming client request MUST be matched to a Listener to
@@ -105,12 +103,12 @@ pub struct Listener {
105
103
/// Implementations MUST apply Hostname matching appropriately for each of
106
104
/// the following protocols:
107
105
///
108
- /// * TLS: The Listener Hostname MUST match the SNI. * HTTP: The Listener
109
- /// Hostname MUST match the Host header of the request. * HTTPS: The
110
- /// Listener Hostname SHOULD match at both the TLS and HTTP protocol layers
111
- /// as described above. If an implementation does not ensure that both the
112
- /// SNI and Host header match the Listener hostname, it MUST clearly document
113
- /// that.
106
+ /// * TLS: The Listener Hostname MUST match the SNI.
107
+ /// * HTTP: The Listener Hostname MUST match the Host header of the request.
108
+ /// * HTTPS: The Listener Hostname SHOULD match at both the TLS and HTTP protocol
109
+ /// layers as described above. If an implementation does not ensure that both the
110
+ /// SNI and Host header match the Listener hostname, it MUST clearly document
111
+ /// that.
114
112
///
115
113
/// For HTTPRoute and TLSRoute resources, there is an interaction with the
116
114
/// `spec.hostnames` array. When both listener and route specify hostnames,
0 commit comments