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

Add http/2 support #292

Open
sereinity opened this Issue May 2, 2018 · 2 comments

Comments

3 participants
@sereinity

sereinity commented May 2, 2018

reqwest should support http/2 and use it by default if the server support it.

By example, when querying https://http2.io/ the server tells us that we are using {"protocol": "HTTP/1.1"}, but with curl (by example) we are getting {"protocol": "HTTP/2.0"}

@kzys

This comment has been minimized.

kzys commented Jun 27, 2018

ANPN support would be needed on native-tls.

Apparently openssl and security-framework are supporting ALPN on master. schannel is not supporting that, but there is a PR (steffengy/schannel-rs#49).

@seanmonstar seanmonstar added this to the 0.9 milestone Jul 4, 2018

@seanmonstar

This comment has been minimized.

Owner

seanmonstar commented Jul 5, 2018

First important step was just completed: upgrading to hyper 0.12 which has HTTP2 support!

A next step would be to add the ability for native-tls to use ALPN when the backend has support. This would allow reqwest to use it on Linux and macOS, and when support is figured out for Windows, it should end up enabled automatically.

@seanmonstar seanmonstar added the upstream label Jul 5, 2018

@seanmonstar seanmonstar added upstream and removed upstream labels Aug 8, 2018

@seanmonstar seanmonstar removed this from the 0.9 milestone Aug 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment