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

support for http/1.1 -> http2 client upgrade for outbound connections #1502

Open
akshaychitneni opened this issue Aug 21, 2017 · 3 comments
Open
Labels
enhancement Feature requests. Not bugs or questions. help wanted Needs help!

Comments

@akshaychitneni
Copy link

Envoy only supports http2 connections to the upstream hosts with prior knowledge. Any upgrade request from http1.1 to http2 from the client is not supported.

Can this be supported?

Thanks!

@mattklein123 mattklein123 added the enhancement Feature requests. Not bugs or questions. label Aug 21, 2017
@mattklein123
Copy link
Member

This can be supported. There are two ways that I can see this being implemented functionality-wise.

  1. Build functionality into the existing HTTP/2 connection pool that assumes that upgrade is required, but will always succeed. This is relatively simple to implement.

  2. Support a new connection pool which can operate in both HTTP/1 and HTTP/2 modes depending on upgrade. If this is required I would implement an entirely new connection pool implementation. This is a lot more work.

@mattklein123 mattklein123 added the help wanted Needs help! label Oct 28, 2017
@mandarjog
Copy link
Contributor

/subscribe

@swift1911
Copy link

is any progress for this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature requests. Not bugs or questions. help wanted Needs help!
Projects
None yet
Development

No branches or pull requests

4 participants