Hello community,
I have an ignition running in a docker container and a nginx reverse proxy. he reverse proxy is configured to expose Ignition under a prefixed path, such as /ignition , using a URL like:
http://localhost/ignition/web/home
We use the following Nginx settings:
location /ignition/ { rewrite ^/ignition(/.*)$ /$1 break; proxy_pass http://localhost:9088; proxy_http_version 1.1; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Prefix /ignition; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Port $server_port; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }
Inside the Ignition Gateway, we have:
Use Proxy Forwarded Headers = True
Resolve Client Hostnames = False
Despite this, Ignition continues to respond with redirects like:
Location: http://localhost/web/home?0
…instead of respecting the prefix and returning:
Location: http://localhost/ignition/web/home?0
We have confirmed that:
X-Forwarded-Prefix: /ignition is being received by Ignition (tested with curl)
- Proxy forwarding headers are correctly sent
Does anyone had this kind of issue before?