Benjamin M. Schwartz
Benjamin M. Schwartz
Fixed by #2736
@MikeBishop The discussion at IETF 119 leaned toward removing the multiple-IP mode entirely. Are you suggesting that we should keep it?
OK, I've updated this PR to also drop the multiple-IP support entirely.
The distinction is deliberate, precisely because it facilitates using a single URI template for both protocols. As discussed in [Section 5.3](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-connect-tcp-02#section-5.3), the client can use a single template for various...
OK, I see that it doesn't work for connect-ip, so connect-ip can only be supported by probing or with an out-of-band signal (or with an ecosystem restriction that connect-ip servers...
@davidben Yes, this is why the special-case for "." makes sense in AliasMode. The goal of this text is to allow clients to say "The requested service does not exist"...
No, the presence of "any AliasMode HTTPS RRs" is sufficient to trigger the HSTS redirect, even if the RR in question is "null AliasMode".
@Saklad5 AliasMode records chain to each other, so in your example, you are denying the existence of https://example.com as well as https://cdn.example.net. Null aliases do not allow the "target-only" semantics...
> I meant for the first record in my example to be a ServiceMode record. OK. Note that this is not the typical recommended configuration. CDNs normally should own their...
It sounds like we could choose terms to make this a bit clearer.