Josh on Nostr: QUIC is a UDP implementation of HTTP. It's very fast, most modern browsers support ...
QUIC is a UDP implementation of HTTP. It's very fast, most modern browsers support it, but the most popular webservers do not support it. This means if you download a regular open source copy of haproxy or nginx for your website, you will not have HTTP3 as an option.
I stumbled into a rabbit hole of autism. The short is, OpenSSL wants the code for QUIC (which is quite complicated) under Apache2. Google provides QUIC under ISC.
https://github.com/openssl/openssl/pull/8797#issuecomment-502105619
There is functionally identical, except ISC doesn't explicitly provide Patent rights.
https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses
Google refuses to relicense QUIC under Apache.
So now the OpenSSL guys have spent years trying to rewrite the entire QUIC transportation layer on their own so they don't have to use Google's ISC license.
The result: millions of modern websites do not have HTTP3, drafted under RFC 9001 in 2016 and ported to OpenSSL in 2019.
https://datatracker.ietf.org/doc/rfc9001/
I stumbled into a rabbit hole of autism. The short is, OpenSSL wants the code for QUIC (which is quite complicated) under Apache2. Google provides QUIC under ISC.
https://github.com/openssl/openssl/pull/8797#issuecomment-502105619
There is functionally identical, except ISC doesn't explicitly provide Patent rights.
https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses
Google refuses to relicense QUIC under Apache.
So now the OpenSSL guys have spent years trying to rewrite the entire QUIC transportation layer on their own so they don't have to use Google's ISC license.
The result: millions of modern websites do not have HTTP3, drafted under RFC 9001 in 2016 and ported to OpenSSL in 2019.
https://datatracker.ietf.org/doc/rfc9001/