keval shah eb2473914e fix(docker): force HTTP/1.1 on frontend nginx upstream proxy (#9010) (#13725) ...

fix(docker): force HTTP/1.1 on frontend nginx upstream proxy

The frontend nginx config proxied to the backend without setting
proxy_http_version, so nginx used its default of HTTP/1.0 for the
upstream requests. Behind an HTTP/1.1-only proxy (e.g. an Istio/Envoy
service-mesh sidecar) those requests are rejected with HTTP 426 Upgrade
Required, breaking /api, /health, and /health_check.

Set proxy_http_version 1.1 explicitly on every proxy_pass block in both
default.conf.template (rendered into the production frontend image) and
nginx.conf. This is version-independent and keeps working regardless of
which nginx the image ships (the image pins nginx 1.28.0, whose upstream
default is still HTTP/1.0).

Verified with the pinned nginx image in front of an HTTP/1.1-only mock
upstream: /api, /health, /health_check return 200 and nginx forwards
upstream as HTTP/1.1 (was 426 / HTTP/1.0 before the fix).

Fixes #9010

2026-06-19 14:59:03 -07:00

..

build_and_push_frontend.Dockerfile

ci: update docker image configuration for secure deployments (#5259)

2024-12-13 22:38:55 +00:00

default.conf.template

fix(docker): force HTTP/1.1 on frontend nginx upstream proxy (#9010) (#13725)

2026-06-19 14:59:03 -07:00

nginx.conf

fix(docker): force HTTP/1.1 on frontend nginx upstream proxy (#9010) (#13725)

2026-06-19 14:59:03 -07:00

start-nginx.sh

fix: Allow upload limit increase in kubernetes deployment (#7664)

2025-06-03 11:53:08 +00:00