Description:
Describe the desired behavior, what scenario it enables and how it
would be used.
wrt discussion
I have a setup where the envoy gateway is located in front of ingress-nginx. As a backend service there is a websocket service (websocat image) and its ingress is used as an fqdn Backend target for envoy gateway. I've tried a scenario with tls passthrough from envoy sandbox configurations and everything was working fine. Then I tried WSS -> WSS scenario with envoy gateway. From envoy-gw documentation it looked like all the necessary upgrade_configs configurations would be present by default (and it was the case), but I'm having 400 errors on ingress-nginx with the following messages nearby:
client sent unknown pseudo-header ":protocol" while reading client request headers
I believe that @zhaohuabing suggested
to default to HTTP/1.1 when the AppProtocolType of a Backend is gateway.envoyproxy.io/ws or gateway.envoyproxy.io/wss
[optional Relevant Links:]
Any extra documentation required to understand the issue.
Description:
wrt discussion
I believe that @zhaohuabing suggested
[optional Relevant Links:]