Why Do Envoy Gateways Return 404 When :authority and SNI Mismatch in HTTP/2?

In many Envoy‑based gateways, enabling HTTP/2 can cause intermittent 404 errors because the :authority header and the TLS SNI value differ, especially when using wildcard certificates and multi‑domain routing, and this article explains the root cause and multiple mitigation strategies.

421Cloud NativeEnvoy

0 likes · 14 min read

Why Do Envoy Gateways Return 404 When :authority and SNI Mismatch in HTTP/2?