You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
seanmonstar opened this issue
Apr 13, 2018
· 3 comments
Labels
A-serverArea: server.C-featureCategory: feature. This is adding a new feature.E-mediumEffort: medium. Some knowledge of how hyper internal works would be useful.
I haven't personally thought out an exact implementation yet... One way could be for server::conn::Connection to be able to inspect a returned error, and if it's a parse error, try to take the IO and read buffer back out and use them to try the h2::server::handshake...
If an HTTP/1 connection has a parse error, but it starts with the HTTP2 preface, converts the connection automatically into an HTTP2 server connection.
Closes#1486
If an HTTP/1 connection has a parse error, but it starts with the HTTP2 preface, converts the connection automatically into an HTTP2 server connection.
Closeshyperium#1486
A-serverArea: server.C-featureCategory: feature. This is adding a new feature.E-mediumEffort: medium. Some knowledge of how hyper internal works would be useful.
This would be a next step to allowing the server to have HTTP2 support on by default.
The text was updated successfully, but these errors were encountered: