Open MihaZupan opened 5 months ago
From https://github.com/dotnet/aspire/issues/1818
We support many combinations of requests and proxies, but we don't allow non-https HTTP/2 when talking through an HTTP(s) proxy.
This scenario currently gets blocked because we pick a HttpConnectionKind.Proxy pool variant here, which is limited to HTTP/1.1.
HttpConnectionKind.Proxy
Similarly to how we use the CONNECT tunnel for non-https WebSockets, we could proxy non-HTTPS H2 that way as well (as long as the policy used isn't RequestVersionOrLower).
RequestVersionOrLower
Tagging subscribers to this area: @dotnet/ncl See info in area-owners.md if you want to be subscribed.
From https://github.com/dotnet/aspire/issues/1818
We support many combinations of requests and proxies, but we don't allow non-https HTTP/2 when talking through an HTTP(s) proxy.
This scenario currently gets blocked because we pick a
HttpConnectionKind.Proxy
pool variant here, which is limited to HTTP/1.1.Similarly to how we use the CONNECT tunnel for non-https WebSockets, we could proxy non-HTTPS H2 that way as well (as long as the policy used isn't
RequestVersionOrLower
).