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
Feb 27, 2019
· 0 comments
Labels
A-clientArea: client.A-http1Area: HTTP/1 specific.C-bugCategory: bug. Something is wrong. This is bad!E-easyEffort: easy. A task that would be a great starting point for a new contributor.
While the Server and Client will both coerce Version::HTTP_2 to HTTP_11, the client::conn::SendRequest doesn't do that. Thus, this panic is triggered.
It seems best to just add a case for it just like there is in the server encode path.
The text was updated successfully, but these errors were encountered:
seanmonstar
added
C-bug
Category: bug. Something is wrong. This is bad!
A-client
Area: client.
E-easy
Effort: easy. A task that would be a great starting point for a new contributor.
A-http1
Area: HTTP/1 specific.
labels
Feb 27, 2019
A-clientArea: client.A-http1Area: HTTP/1 specific.C-bugCategory: bug. Something is wrong. This is bad!E-easyEffort: easy. A task that would be a great starting point for a new contributor.
While the
Server
andClient
will both coerceVersion::HTTP_2
toHTTP_11
, theclient::conn::SendRequest
doesn't do that. Thus, this panic is triggered.It seems best to just add a case for it just like there is in the server encode path.
The text was updated successfully, but these errors were encountered: