Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configuration: option to use h2/http1.1 based on header information #679

Closed
junr03 opened this issue Feb 11, 2020 · 0 comments · Fixed by #697
Closed

configuration: option to use h2/http1.1 based on header information #679

junr03 opened this issue Feb 11, 2020 · 0 comments · Fixed by #697
Assignees

Comments

@junr03
Copy link
Member

junr03 commented Feb 11, 2020

Right now all configured clusters go over http1.1. Until #502 is supported we should create the option to have streams decide what protocol version to support, and have backing configuration for clusters configured for http1.1 and h2.

@junr03 junr03 added this to the v0.3 "Secondi" milestone Feb 11, 2020
@junr03 junr03 self-assigned this Feb 11, 2020
@goaway goaway assigned goaway and unassigned junr03 Feb 12, 2020
@junr03 junr03 assigned junr03 and unassigned goaway Feb 20, 2020
junr03 added a commit that referenced this issue Feb 21, 2020
…upstream requests (#697)

Description: this PR adds the ability to decide what protocol to use for upstream requests. Note that this will be unnecessary once ALPN works for upstream requests (#502)
Risk Level: low
Testing: updated unit tests
Docs Changes: updated docs

Fixes #679 

Signed-off-by: Michael Rebello <[email protected]>

Co-authored-by: Michael Rebello <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants