Support HTTP/2.0

[clue]

No description provided.

[maciejmrozinski]

Hi,

Do You have any WIP for this, plans, ideas how to implement this? Or maybe a good point of start will be after 1.0 release when internal API and classes will be stabilized? Any info appreciated :)

[clue]

The main focus is currently on getting the v1.0.0 out. As such, there are currently no immediate plans to build this from our end (no demand at the moment), but I suppose we would be really happy to accept PRs 👍

[WyriHaximus]

@clue I would like to see HTTP/2 support after 1.0.0 is out. But we need certain features for that first.

[maciejmrozinski]

Ok, so i will get back to topic after 1.0 :)

[cordoval]

how does this have to do with version 2? i thought version 2 is an nginx thing rather?

[clue]

@cordoval Yes, there are a number of use cases where you can use this project without requiring HTTP/2.0. For example, if you're using this project behind a reverse proxy (such as nginx) that is capable of speaking HTTP/2.0 to the client and forwards this as HTTP/1.x to this library, then you can probably live without native HTTP/2.0 support here.

However, we still want to look into implementing HTTP/2.0 here as well so that this can also be used without a reverse proxy 👍 In the meantime, there are plenty of HTTP/2.0 proxies that can be used as above 👍

[WyriHaximus]

@clue && @cordoval in fact most of my own sites are running react/http behind nginx that handles HTTP/2.0 and certificates for all the different sites hosted on that box.

[cordoval]

nice man, good to know

hey have you news where is igorw? 👴 just curious

[valzargaming]

Are there any plans to support HTTP/3?

[clue]

@valzargaming I can definitely see us implementing HTTP/3 in the future, but baby steps first! In the meantime, using a reverse proxy to handle HTTP/2 and HTTP/3 is perfectly reasonable for many uses, but we definitely welcome contributions to help us land full support here as well 👍

[SimonFrings]

It seems like this ticket is open for quite a while now. I want to avoid issues and pull request laying around for too long, but this depends on each topic. I think HTTP/2 support will come in the future, but I don't think there's something scheduled yet.

With that said we could close this ticket for now and reopen it once there are more detailed plans for HTTP/2 support, or we could leave it open, I will leave this decision to @clue as he opened this up 👍

[WyriHaximus]

It seems like this ticket is open for quite a while now. I want to avoid issues and pull request laying around for too long, but this depends on each topic. I think HTTP/2 support will come in the future, but I don't think there's something scheduled yet.

IMHO we still want to do this but need to do some internal refactoring first. It is very much on my list of things to add.