Open danroot opened 5 years ago
@danroot it's not supported yet, I will put this in To-Do list.
+1
I think it is really difficult issue to make. I don't know how can I help to make this feature realize.
Perhaps is best to first write out a summary of the biggest differences in protocol and maybe triage what is needed. For example, I don't think rest-client would benefit from understanding HTTP Push. Or at least it's not the most urgent thing to support. Probably what most people want is to be able to just send a get or post with HTTP/2 in the request and have mostly the same experience. But maybe it's also worth verifying that first too?
@Huachao how can we help with this issue? if you have a concrete idea how to fix it one of us can create a PR. I think by the time this becomes an important feature.
Just adding that you cannot explicitly request an upgrade either:
GET /order/123 HTTP/1.1
Host: api.company.com
Connection: upgrade
Upgrade: HTTP/2.0
@Huachao Is there any progress on this issue yet??
I have an endpoint I tested with an online tool that says HTTP/2 is working correctly. However, when I specify that to restclient like this: GET https://api.somecompany.com/prod/v1/login HTTP/2.0 The server still responds with HTTP 1.1 200 OK. Am I misunderstanding HTTP/2, is this not supported yet, or is there some other flag I can set to test HTTP2 from restclient?