3 ms·
Can you post the relevant part of the spec or discussion of it? This sounds wack but I'm not seeing it.
by no_time 3y ago
Can you post the relevant part of the spec or discussion of it? This sounds wack but I'm not seeing it.
- superkuh 3y agoThe spec suggested defaults don't matter when all current HTTP/3 implementations will not let compiled software users connect to a site with a self-signed cert (or none at all). But also the spec itself is bad: "MUST" in capital letters when talking about setting up the HTTP3 endpoint and verifying the cert. https://datatracker.ietf.org/doc/rfc9114/ https://datatracker.ietf.org/doc/rfc9114/ There are compile-time flags you can use to enable it in the QUIC HTTP/3 libs you can then manually link when compiling your personal browser. But with Google/Microsoft/Apple/Mozilla browser binaries used by the public they will not be able to connect.