envoyproxy/gateway

Fix conformance for GatewayHTTPSListenerDetectMisdirectedRequests

開放

#5,879 建立於 2025年5月1日

 (14 則留言) (2 個反應) (1 位負責人)Go (802 個分叉)auto 404
area/envoyhelp wanted

倉庫指標

星標
 (2,871 顆星)
PR 合併指標
 (PR 指標待抓取)

描述

We should return 421 when http/2 connection coalescing is detected

one workaround for now, is to disable http/2 ALPN when overlapping hostnames are detected, with the OverlappingTLSConfig condition added to the listeners https://gateway-api.sigs.k8s.io/geps/gep-3567/

I might be technically not deep enough into this https://gateway-api.sigs.k8s.io/geps/gep-3567/ states an option b of returning 421 for this. Is there a reason that envoy gateway is doing that which i am missing and/or could this be tracked as a followup in this or a new issue? Ideally it would be nice to not break http2 support like this :)

Originally posted by @MTRNord in #2675

貢獻者指南