Repository navigation
Why not using Host header to autodetect public URL when behind reverse proxy? #19778
AndreaVida
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
From Using a reverse proxy guide it seems supported ways to let Keycloak autodetect the original public URL when deployed behind a reverse proxy (proxy mode = edge) are following headers:
Forwarded
Non-standard X-Forwarded
Non-standard X-Forwarded-*, such as X-Forwarded-For, X-Forwarded-Proto, X-Forwarded-Host, and X-Forwarded-Port
However, while those headers are not always present, a very common header is Host which is typically set by clients. Why not using this header as a last resort fallback if none of the previous are present?
All reactions