mirror of
https://github.com/keycloak/keycloak.git
synced 2026-01-10 15:32:05 -03:30
764ca50fc4
* Upgrade to Quarkus 3.18.2 Closes #37056 Signed-off-by: Václav Muzikář <vmuzikar@redhat.com> * Update docs/documentation/upgrading/topics/changes/changes-26_2_0.adoc Co-authored-by: Alexander Schwartz <alexander.schwartz@gmx.net> Signed-off-by: Václav Muzikář <vaclav@muzikari.cz> --------- Signed-off-by: Václav Muzikář <vmuzikar@redhat.com> Signed-off-by: Václav Muzikář <vaclav@muzikari.cz> Co-authored-by: Alexander Schwartz <alexander.schwartz@gmx.net>
16 lines
887 B
Plaintext
16 lines
887 B
Plaintext
== Breaking changes
|
|
|
|
Breaking changes are identified as requiring changes from existing users to their configurations.
|
|
|
|
=== Changes to port behaviour with the `X-Forwarded-Host` header
|
|
|
|
The `X-Forwarded-Host` header can optionally also contain the port. In previous versions when the port was omitted from the header,
|
|
{project_name} fell back to the actual request port. For example if {project_name} was listening on port 8080 and the request contained
|
|
`X-Forwarded-Host: example.com` header, the resolved URL was `+http://example.com:8080+`.
|
|
|
|
This is now changed and omitting the port results in removing it from the resolved URL. The resolved URL from the previous example
|
|
would now be `http://example.com`.
|
|
|
|
To mitigate that, either make your reverse proxy include the port in the `X-Forwarded-Host` header or configure it to set
|
|
the `X-Forwarded-Port` header with the desired port.
|