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
@cyal1 Thanks for opening this issue. The HTTP protocol is something negotiated by the client and not enforced by the server. To force it, you should explicitly set your client to use HTTP 1.X, and, I suppose, it's also necessary to skip alpn/npn negotiation. For example, with curl, the following command performs the request with HTTP 1.1:
net/http supports natively http/2 upgrade upon client request. I guess in this case we would need to add a CLI flag to specify explicitly which protocol to use as it needs to be set through TLSNextProto in the http server settings:
Activity
Mzack9999 commentedon Sep 13, 2021
@cyal1 Thanks for opening this issue. The HTTP protocol is something negotiated by the client and not enforced by the server. To force it, you should explicitly set your client to use HTTP 1.X, and, I suppose, it's also necessary to skip alpn/npn negotiation. For example, with curl, the following command performs the request with HTTP 1.1:
cyal1 commentedon Sep 18, 2021
hello, I want the service only support http/1.1
Mzack9999 commentedon Oct 15, 2021
net/httpsupports natively http/2 upgrade upon client request. I guess in this case we would need to add a CLI flag to specify explicitly which protocol to use as it needs to be set throughTLSNextProtoin the http server settings: