HTTP/2.0 and HTTP/3.0

[PatrickDahlin]

Support for HTTP/2.0 and the upcoming HTTP/3.0 would be epic. I know this requires some bigger changes (I think) since 3.0 needs multiple UDP connections but it should be possible.

I would try looking into how to do it using luv but it's quite a complex system built already.
Would this be something that could be implemented sufficiently well while still keeping the api stable.

[Bilal2453]

Due to the nature of HTTP itself, this can be implemented without breaking the interface code. But it requires a complete rework of the backend, more specifically, weblit depends on coro-net for its server implementation, which is barely functional as-is, proper HTTP 3.0 is even more time consuming as it requires implementing QUIC first. Nothing particularly impossible or hard, just really time consuming overall, especially if you want an efficient one.
http-codec will also need a major rework to make this possible, which is probably where most of the interface code will go.

If you want HTTP2/3 I advice you to use a reverse proxy for now.