envoyproxy/envoy

Support Upgrade: h2c for upstream clusters

Open

#26,463 建立於 2023年3月30日

在 GitHub 查看
 (3 留言) (5 反應) (1 負責人)C++ (5,373 fork)batch import
enhancementhelp wanted

倉庫指標

Star
 (27,997 star)
PR 合併指標
 (平均合併 8天) (30 天內合併 378 個 PR)

描述

Title: Support Upgrade: h2c for upstream clusters

Description:

I have an environment where I have a mixture of HTTP/1.1 (plaintext) and HTTP/2 upstreams. What I'd like to be able to do is configure Envoy in such a way that it can automatically negotiate to use HTTP/1.1 or HTTP/2 without me manually specifying this. ALPN would be ideal here of course but nothing is currently using TLS so (as I understand things) that won't work.

Envoy already supports Upgrade: h2c for downstreams, would it be possible to get support for this for upstreams? I do understand that h2c is relatively abandonded/outdataed in favour of ALPN, but as I said that is not useable for me in my current circumstancs.

[optional Relevant Links:]

https://en.wikipedia.org/wiki/HTTP/1.1_Upgrade_header https://github.com/envoyproxy/envoy/issues/7161

貢獻者指南