fix: Enable proxy forwarding for ingress nginx headers

- Add quarkus.http.proxy.* properties to read X-Forwarded-* headers
- Fixes redirect issue where Swagger UI redirects to /q/swagger-ui/ instead of /lions-user-manager/q/swagger-ui/
- Allows Quarkus to reconstruct original URL from ingress headers
This commit is contained in:
dahoud
2026-02-27 05:40:02 +00:00
parent bb5a2ec8c7
commit 633dcc3f86

View File

@@ -12,6 +12,12 @@ quarkus.http.port=8080
# quarkus.http.root-path est une propriete build-time — passee via -Dquarkus.http.root-path dans le Dockerfile # quarkus.http.root-path est une propriete build-time — passee via -Dquarkus.http.root-path dans le Dockerfile
quarkus.http.cors.origins=${CORS_ORIGINS:https://users.lions.dev,https://btpxpress.lions.dev,https://admin.lions.dev} quarkus.http.cors.origins=${CORS_ORIGINS:https://users.lions.dev,https://btpxpress.lions.dev,https://admin.lions.dev}
# Proxy forwarding pour ingress nginx (permet à Quarkus de lire X-Forwarded-* headers)
quarkus.http.proxy.proxy-address-forwarding=true
quarkus.http.proxy.allow-x-forwarded=true
quarkus.http.proxy.enable-forwarded-host=true
quarkus.http.proxy.enable-forwarded-prefix=true
# ============================================ # ============================================
# OIDC Configuration PROD # OIDC Configuration PROD
# ============================================ # ============================================