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
{{ message }}
Repository navigation
support for http/1.1 -> http2 client upgrade for outbound connections #1502
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!
Reacted by Bastian Kuberek, Raphael Gruber, Paweł Szczepański, m1o1, Brandon, chuong vu, Greg Cobb, Amila Senadheera, Eugen Chirilov, Huabing (Robin) Zhao and 2 more
This can be supported. There are two ways that I can see this being implemented functionality-wise.
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.
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.
Activity
mattklein123 commentedon Aug 21, 2017
This can be supported. There are two ways that I can see this being implemented functionality-wise.
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.
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.
mandarjog commentedon May 17, 2018
/subscribe
swift1911 commentedon May 9, 2019
is any progress for this issue?