3 ms·
I can't find much about this in the HTTP/3 spec. Validation of certificates must be done according to section 4.3.4 of RFC9110 which explicitly spells out that
by jeroenhd 4y ago
I can't find much about this in the HTTP/3 spec. Validation of certificates must be done according to section 4.3.4 of RFC9110 which explicitly spells out that browsers must either get permission to continue or abort, but that's up to the browser to decide.
I can find some references to Chrome's QUIC not supporting self signed certificates, but I can't find any source that says that WebKit and Firefox made the same decision. Do you happen to know a self signed HTTP/3 URL that I can test this with?
Browsers choosing to break self signed certificates can happen even with HTTP 0.9. All they need to do is require the user to type the bypass phrase ("thisisunsafe" in the Chrome error screen) on any certificate validation error and enable HTTPS only mode. This has nothing to do with spec. Browsers have even removed spec implementations for HTTP/2 spec (HTTP push) after a few years.