Sync web site with Quarkus documentation

quarkusbot · quarkusbot · commit f098892e62bb · 2025-02-27T17:26:38.000Z
diff --git a/_generated-doc/3.15/config/quarkus-all-config.adoc b/_generated-doc/3.15/config/quarkus-all-config.adoc
@@ -11467,7 +11467,7 @@ a| [[quarkus-vertx-http_quarkus-http-proxy-allow-forwarded]] [.property-path]##l
 
 [.description]
 --
-If this is true and proxy address forwarding is enabled then the standard `Forwarded` header will be used. In case the not standard `X-Forwarded-For` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-x-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-++*++` headers from the client.
+If this is true and proxy address forwarding is enabled then the standard `Forwarded` header will be used. In case the not standard `X-Forwarded-For` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-x-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-++*++` headers from the client.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -11484,7 +11484,7 @@ a| [[quarkus-vertx-http_quarkus-http-proxy-allow-x-forwarded]] [.property-path]#
 
 [.description]
 --
-If either this or `allow-forwarded` are true and proxy address forwarding is enabled then the not standard `Forwarded` header will be used. In case the standard `Forwarded` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-++*++` headers from the client.
+If either this or `allow-forwarded` are true and proxy address forwarding is enabled then the not standard `Forwarded` header will be used. In case the standard `Forwarded` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-++*++` headers from the client.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -12850,7 +12850,7 @@ a| [[quarkus-vertx-http_quarkus-management-proxy-allow-forwarded]] [.property-pa
 
 [.description]
 --
-If this is true and proxy address forwarding is enabled then the standard `Forwarded` header will be used. In case the not standard `X-Forwarded-For` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-x-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-++*++` headers from the client.
+If this is true and proxy address forwarding is enabled then the standard `Forwarded` header will be used. In case the not standard `X-Forwarded-For` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-x-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-++*++` headers from the client.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -12867,7 +12867,7 @@ a| [[quarkus-vertx-http_quarkus-management-proxy-allow-x-forwarded]] [.property-
 
 [.description]
 --
-If either this or `allow-forwarded` are true and proxy address forwarding is enabled then the not standard `Forwarded` header will be used. In case the standard `Forwarded` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-++*++` headers from the client.
+If either this or `allow-forwarded` are true and proxy address forwarding is enabled then the not standard `Forwarded` header will be used. In case the standard `Forwarded` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-++*++` headers from the client.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -69999,6 +69999,23 @@ endif::add-copy-button-to-env-var[]
 |string
 |`/`
 
+a| [[quarkus-security-webauthn_quarkus-webauthn-enable-callback-endpoint]] [.property-path]##link:#quarkus-security-webauthn_quarkus-webauthn-enable-callback-endpoint[`quarkus.webauthn.enable-callback-endpoint`]##
+
+[.description]
+--
+Set to `true` if you want to enable the default registration and login endpoint at `/q/webauthn/callback`.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_WEBAUTHN_ENABLE_CALLBACK_ENDPOINT+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_WEBAUTHN_ENABLE_CALLBACK_ENDPOINT+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 
 h|[.extension-name]##SmallRye GraphQL##
 h|Type
diff --git a/_generated-doc/3.15/config/quarkus-security-webauthn.adoc b/_generated-doc/3.15/config/quarkus-security-webauthn.adoc
@@ -365,6 +365,23 @@ endif::add-copy-button-to-env-var[]
 |string
 |`/`
 
+a| [[quarkus-security-webauthn_quarkus-webauthn-enable-callback-endpoint]] [.property-path]##link:#quarkus-security-webauthn_quarkus-webauthn-enable-callback-endpoint[`quarkus.webauthn.enable-callback-endpoint`]##
+
+[.description]
+--
+Set to `true` if you want to enable the default registration and login endpoint at `/q/webauthn/callback`.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_WEBAUTHN_ENABLE_CALLBACK_ENDPOINT+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_WEBAUTHN_ENABLE_CALLBACK_ENDPOINT+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 |===
 
 ifndef::no-duration-note[]
diff --git a/_generated-doc/3.15/config/quarkus-security-webauthn_quarkus.webauthn.adoc b/_generated-doc/3.15/config/quarkus-security-webauthn_quarkus.webauthn.adoc
@@ -365,6 +365,23 @@ endif::add-copy-button-to-env-var[]
 |string
 |`/`
 
+a| [[quarkus-security-webauthn_quarkus-webauthn-enable-callback-endpoint]] [.property-path]##link:#quarkus-security-webauthn_quarkus-webauthn-enable-callback-endpoint[`quarkus.webauthn.enable-callback-endpoint`]##
+
+[.description]
+--
+Set to `true` if you want to enable the default registration and login endpoint at `/q/webauthn/callback`.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_WEBAUTHN_ENABLE_CALLBACK_ENDPOINT+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_WEBAUTHN_ENABLE_CALLBACK_ENDPOINT+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 |===
 
 ifndef::no-duration-note[]
diff --git a/_generated-doc/3.15/config/quarkus-vertx-http_quarkus.http.adoc b/_generated-doc/3.15/config/quarkus-vertx-http_quarkus.http.adoc
@@ -2805,7 +2805,7 @@ a| [[quarkus-vertx-http_quarkus-http-proxy-allow-forwarded]] [.property-path]##l
 
 [.description]
 --
-If this is true and proxy address forwarding is enabled then the standard `Forwarded` header will be used. In case the not standard `X-Forwarded-For` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-x-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-++*++` headers from the client.
+If this is true and proxy address forwarding is enabled then the standard `Forwarded` header will be used. In case the not standard `X-Forwarded-For` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-x-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-++*++` headers from the client.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -2822,7 +2822,7 @@ a| [[quarkus-vertx-http_quarkus-http-proxy-allow-x-forwarded]] [.property-path]#
 
 [.description]
 --
-If either this or `allow-forwarded` are true and proxy address forwarding is enabled then the not standard `Forwarded` header will be used. In case the standard `Forwarded` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-++*++` headers from the client.
+If either this or `allow-forwarded` are true and proxy address forwarding is enabled then the not standard `Forwarded` header will be used. In case the standard `Forwarded` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-++*++` headers from the client.
 
 
 ifdef::add-copy-button-to-env-var[]
diff --git a/_generated-doc/3.15/config/quarkus-vertx-http_quarkus.management.adoc b/_generated-doc/3.15/config/quarkus-vertx-http_quarkus.management.adoc
@@ -1169,7 +1169,7 @@ a| [[quarkus-vertx-http_quarkus-management-proxy-allow-forwarded]] [.property-pa
 
 [.description]
 --
-If this is true and proxy address forwarding is enabled then the standard `Forwarded` header will be used. In case the not standard `X-Forwarded-For` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-x-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-++*++` headers from the client.
+If this is true and proxy address forwarding is enabled then the standard `Forwarded` header will be used. In case the not standard `X-Forwarded-For` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-x-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-++*++` headers from the client.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -1186,7 +1186,7 @@ a| [[quarkus-vertx-http_quarkus-management-proxy-allow-x-forwarded]] [.property-
 
 [.description]
 --
-If either this or `allow-forwarded` are true and proxy address forwarding is enabled then the not standard `Forwarded` header will be used. In case the standard `Forwarded` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-++*++` headers from the client.
+If either this or `allow-forwarded` are true and proxy address forwarding is enabled then the not standard `Forwarded` header will be used. In case the standard `Forwarded` header is enabled and detected on HTTP requests, the standard header has the precedence. Activating this together with `quarkus.http.proxy.allow-forwarded` has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-++*++` headers from the client.
 
 
 ifdef::add-copy-button-to-env-var[]
diff --git a/_versions/3.15/guides/_attributes.adoc b/_versions/3.15/guides/_attributes.adoc
@@ -1,7 +1,7 @@
 // Common attributes.
 // --> No blank lines (it ends the document header)
 :project-name: Quarkus
-:quarkus-version: 3.15.3
+:quarkus-version: 3.15.3.1
 :quarkus-platform-groupid: io.quarkus.platform
 // .
 :maven-version: 3.9.8
diff --git a/_versions/3.15/guides/context-propagation.adoc b/_versions/3.15/guides/context-propagation.adoc
@@ -135,7 +135,7 @@ them to the client as JSON using xref:rest-json.adoc[Jackson or JSON-B]:
         // Create a REST client to the Star Wars API
         WebClient client = WebClient.create(vertx,
                          new WebClientOptions()
-                          .setDefaultHost("swapi.dev")
+                          .setDefaultHost("swapi.tech")
                           .setDefaultPort(443)
                           .setSsl(true));
         // get the list of Star Wars people, with context capture
diff --git a/_versions/3.15/guides/deploying-to-kubernetes.adoc b/_versions/3.15/guides/deploying-to-kubernetes.adoc
@@ -301,7 +301,7 @@ of secret that contains the required credentials. Quarkus can automatically gene
 quarkus.kubernetes.generate-image-pull-secret=true
 ----
 
-More specifically a `Secret`like the one bellow is genrated:
+More specifically a `Secret` like the one below is generated:
 
 [source,yaml]
 ----
diff --git a/_versions/3.15/guides/http-reference.adoc b/_versions/3.15/guides/http-reference.adoc
@@ -554,7 +554,7 @@ quarkus.http.proxy.trusted-proxies=127.0.0.1 <1>
 ----
 <1> Configure trusted proxy with the IP address `127.0.0.1`. Request headers from any other address are going to be ignored.
 
-Both configurations related to standard and non-standard headers can be combined, although the standard headers configuration will have precedence. However, combining them has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `X-Forwarded` or `X-Forwarded-*` headers from the client.
+Both configurations related to standard and non-standard headers can be combined, although the standard headers configuration will have precedence. However, combining them has security implications as clients can forge requests with a forwarded header that is not overwritten by the proxy. Therefore, proxies should strip unexpected `Forwarded` or `X-Forwarded-*` headers from the client.
 
 Supported forwarding address headers are:
 
diff --git a/_versions/3.15/guides/mongodb-panache.adoc b/_versions/3.15/guides/mongodb-panache.adoc
@@ -242,7 +242,7 @@ List<String> namesButEmmanuels = persons
     .collect(Collectors.toList());
 ----
 
-NOTE: A `persistOrUpdate()` method exist that persist or update an entity in the database, it uses the __upsert__ capability of MongoDB to do it in a single query.
+NOTE: A `persistOrUpdate()` method persists or updates an entity in the database, it uses the __upsert__ capability of MongoDB to do it in a single query.
 
 === Adding entity methods
 
@@ -410,7 +410,7 @@ List<String> namesButEmmanuels = persons
     .collect(Collectors.toList());
 ----
 
-NOTE: A `persistOrUpdate()` method exist that persist or update an entity in the database, it uses the __upsert__ capability of MongoDB to do it in a single query.
+NOTE: A `persistOrUpdate()` method persists or updates an entity in the database, it uses the __upsert__ capability of MongoDB to do it in a single query.
 
 NOTE: The rest of the documentation show usages based on the active record pattern only,
 but keep in mind that they can be performed with the repository pattern as well.
diff --git a/_versions/3.15/guides/security-webauthn.adoc b/_versions/3.15/guides/security-webauthn.adoc
@@ -496,6 +496,16 @@ public class MyWebAuthnSetup implements WebAuthnUserProvider {
 }
 ----
 
+== Configuration
+
+Because we want to delegate login and registration to the default Quarkus WebAuthn endpoints, we need to enable them
+in configuration (`src/main/resources/application.properties`):
+
+[source,properties]
+----
+quarkus.webauthn.enable-callback-endpoint=true
+----
+
 == Writing the HTML application
 
 We now need to write a web page with links to all our APIs, as well as a way to register a new user, login, and logout,
@@ -743,6 +753,8 @@ The Quarkus WebAuthn extension comes out of the box with these REST endpoints pr
 
 This returns a 204 with no body.
 
+NOTE: This is only enabled if the `quarkus.webauthn.enable-callback-endpoint` configuration is set to `true`.
+
 === Obtain a login challenge
 
 `POST /q/webauthn/login`: Set up and obtain a login challenge
@@ -804,6 +816,8 @@ This returns a 204 with no body.
 
 This returns a 204 with no body.
 
+NOTE: This is only enabled if the `quarkus.webauthn.enable-callback-endpoint` configuration is set to `true`.
+
 === Logout
 
 `GET /q/webauthn/logout`: Logs you out
@@ -927,6 +941,9 @@ allows you to create two separate endpoints for handling login and registration
 In most cases you can keep using the `/q/webauthn/login` and `/q/webauthn/register` challenge-initiating
 endpoints, because this is not where custom logic is required.
 
+NOTE: When setting up your own login and registration endpoints, you don't need to enable the default endpoints, so you can
+remove the `quarkus.webauthn.enable-callback-endpoint` configuration.
+
 For example, here's how you can handle a custom login and register action:
 
 [source,java]
diff --git a/_versions/3.15/guides/writing-native-applications-tips.adoc b/_versions/3.15/guides/writing-native-applications-tips.adoc
@@ -197,7 +197,7 @@ public class MyReflectionConfiguration {
 }
 ----
 
-Note: By default the `@RegisterForReflection` annotation will also registered any potential nested classes for reflection. If you want to avoid this behavior, you can set the `ignoreNested` attribute to `true`.
+Note: By default the `@RegisterForReflection` annotation will also register any potential nested classes for reflection. If you want to avoid this behavior, you can set the `ignoreNested` attribute to `true`.
 
 ==== Using a configuration file
 
