René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"HTTP/3 support","articleBody":"As far as I can tell, there's currently no open issue explicitly tracking for QUIC or HTTP/3. Selfishly I'm very interested in knowing when this is available, so I'd personally find it very valuable to have an issue (this issue) tracking the current state and progress.\r\n\r\nTo document the current state:\r\n\r\n* QUIC was tracked in https://github.com/nodejs/node/issues/23064\r\n* That was closed when the [experimental implementation](https://github.com/nodejs/node/pull/30943) was started\r\n* That entire implementation was later [removed](https://github.com/nodejs/node/pull/37067) due to lack of support in OpenSSL\r\n* We've now [moved](https://github.com/nodejs/node/pull/38512) to the Quictls fork of OpenSSL to avoid being blocked by OpenSSL's [approach](https://daniel.haxx.se/blog/2021/10/25/the-quic-api-openssl-will-not-provide/) to implementing QUIC\r\n* There's a draft QUIC implementation being worked on [here](https://github.com/nodejs/node/pull/44325).\r\n* That QUIC implementation is a prerequisite for any HTTP/3 implementation (so we're still a way off)\r\n\r\n@jasnell I think you've been doing most of the legwork here (thank you!), is that about right?\r\n\r\nFeel free to close this if it's a problem to create feature requests like this, but I suspect there's likely to be lots of people interested in QUIC \u0026 HTTP/3, so a central issue documenting it is pretty useful imo.","author":{"url":"https://github.com/pimterry","@type":"Person","name":"pimterry"},"datePublished":"2021-04-30T08:08:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":60},"url":"https://github.com/38478/node/issues/38478"}