* Fix WebSocket proxy to respect PassHostHeader setting When PassHostHeader is set to false, the regular HTTP proxy correctly sets the Host header to the upstream backend URL. However, the WebSocket proxy was not respecting this setting, causing WebSocket connections to fail when backend services validate the Host header. This commit: - Adds passHostHeader parameter to newWebSocketReverseProxy() - Applies setProxyUpstreamHostHeader() when PassHostHeader=false - Ensures consistent behavior between HTTP and WebSocket proxies Fixes #3288 Signed-off-by: Pascal Schmiel <pascal.schmiel@gmail.com> * chore(): add tests, update changelog Signed-off-by: Pascal Schmiel <pascal.schmiel@gmail.com> --------- Signed-off-by: Pascal Schmiel <pascal.schmiel@gmail.com> |
||
|---|---|---|
| .. | ||
| file.go | ||
| file_test.go | ||
| http.go | ||
| http_test.go | ||
| proxy.go | ||
| proxy_test.go | ||
| rewrite.go | ||
| rewrite_test.go | ||
| static.go | ||
| static_test.go | ||
| upstream_suite_test.go | ||