-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP/2 - Enable HTTP/2, ALPN & NPN by default #181
Comments
With the migration to reactor netty, it is possible to enable HTTP2 support on both the server and client sides. Two http2 modes can be enabled:
In my opinion both H2 and H2C need to be supported client side and server side. The administrator will have to decide which one to enable. I would expect a configuration like this for server side:
For client side:
or
|
I did some testing and based on what said here https://projectreactor.io/docs/netty/release/reference/index.html#_protocol_selection , it seems that in our case, on the listener we can support HTTP11+H2 or HTTP11 +H2C. Does it make sense to you too? @pv3nturi |
@hamadodene it shouldn't be a problem since we have different listener for http and https (different port). I don't see a case where we need a listener with H2+H2C |
@aluccaroni I agree with you |
For performance reason enable by default HTTP/2, Application Layer Protocol Negotiation and Next Protocol Negotiation.
We should have all the building blocks (Netty, boringSSL) to do so
The text was updated successfully, but these errors were encountered: