fix: minor updates to the quarkus migration guide (#36011)

closes: #33602

Signed-off-by: Steve Hawkins <shawkins@redhat.com>
This commit is contained in:
Steven Hawkins
2025-01-07 06:34:57 -05:00
committed by GitHub
parent 58c344dfeb
commit 9416e9afdd

View File

@@ -4,7 +4,7 @@
title="Migrating to Quarkus distribution" title="Migrating to Quarkus distribution"
summary="Migrate to the new Quarkus distribution from the legacy WildFly distribution"> summary="Migrate to the new Quarkus distribution from the legacy WildFly distribution">
In Keycloak 17 the default distribution is now powered by Quarkus, while the legacy WildFly powered distribution will still be around until June 2022 we highly recommend starting the migration as soon as possible. Starting with Keycloak 17 the default distribution is now powered by Quarkus, while the legacy WildFly powered distribution will still be around until June 2022 we highly recommend starting the migration as soon as possible.
The new distribution introduces a number of breaking changes, including: The new distribution introduces a number of breaking changes, including:
@@ -108,6 +108,6 @@ Using this new CR you can import Users, Clients and more through the wrapping Re
== Priority of X-Forwarded-* Headers == Priority of X-Forwarded-* Headers
In Quarkus the X-Forwarded-Port header takes precedence over any port included in the X-Forwarded-Host. This differs from the WildFly distribution where a port included in X-Forwarded-Host had priority over X-Forwarded-Port. In Quarkus when using the Hostname V1 feature the X-Forwarded-Port header takes precedence over any port included in the X-Forwarded-Host. This differs from the WildFly distribution where a port included in X-Forwarded-Host had priority over X-Forwarded-Port.
</@tmpl.guide> </@tmpl.guide>