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
duplicateIssues and PRs that are duplicates of other issues or PRs.http2Issues or PRs related to the http2 subsystem.questionIssues that look for answers.
I filed nodejs/http2#189 but seems no discussions at all, wonder is it possible for a http client library gracefully support both http2 and http1 servers? I want the client library to prefer connect by http2, then fallback to http1; I've tried current http2.connect but seems unable to connect if a server does not support http2? current behavior of http2.connect("https://some-no-http2-server") is returned a http2session but got destroyed after tried connection; so the solution I can think of is to use a http2session close event listener if closed almost immediately can try fallback to http1; however this won't be efficient; wonder anyone has better ideas?
since server side has nodejs/http2#125 http2: ALPN fallback to HTTP/1.1 can we have similar API for the http2 client session?
addaleax
added
duplicate
Issues and PRs that are duplicates of other issues or PRs.
http2
Issues or PRs related to the http2 subsystem.
question
Issues that look for answers.
labels
Oct 29, 2017
duplicateIssues and PRs that are duplicates of other issues or PRs.http2Issues or PRs related to the http2 subsystem.questionIssues that look for answers.
I filed nodejs/http2#189 but seems no discussions at all, wonder is it possible for a http client library gracefully support both http2 and http1 servers? I want the client library to prefer connect by http2, then fallback to http1; I've tried current
http2.connect
but seems unable to connect if a server does not support http2? current behavior ofhttp2.connect("https://some-no-http2-server")
is returned a http2session but got destroyed after tried connection; so the solution I can think of is to use a http2sessionclose
event listener if closed almost immediately can try fallback to http1; however this won't be efficient; wonder anyone has better ideas?The text was updated successfully, but these errors were encountered: