On Sun, Jun 30, 2019 at 06:23:36PM +0000, Sam Whited wrote: > On Sun, Jun 30, 2019, at 18:15, Kim Alvefur wrote: > > Please don't. While detecting use of TLS or plain is fairly simple it > > is more complicated to handle both on the same port. I don't know any > > socket handling framework that makes this easy. Usually the TLS > > library takes over the socket and if you inspected the first bytes > > then it fails. > > You don't have to support them both on the same port necessarily, but > since I can't detect if you support it or not I don't have many options > other than to just try it.
You can detect it, it's advertised in DNS. Since a common use case of Direct TLS is to put it on port 443, why don't you also probe that port? -- Zash
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
