From 5f7b0e2b0ee28229dfb42eff7acf30c75fcc00b6 Mon Sep 17 00:00:00 2001 From: Akulov S V Date: Thu, 19 Dec 2024 00:20:18 +0300 Subject: [PATCH] fix --- docs/src/main/asciidoc/rest-client.adoc | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/src/main/asciidoc/rest-client.adoc b/docs/src/main/asciidoc/rest-client.adoc index d53d3de313f048..4c49e0acef7794 100644 --- a/docs/src/main/asciidoc/rest-client.adoc +++ b/docs/src/main/asciidoc/rest-client.adoc @@ -496,11 +496,10 @@ Setting the base URL of the client is **mandatory**, however the REST Client sup [IMPORTANT] ==== -These properties set should not be used in production. +This properties set should not be used in production. ==== -You can configure TLS connection of specific REST client to trust all certificates and disable the hostname verification, -using tls extension. +You can configure TLS connection of specific REST client to trust all certificates and disable the hostname verification using tls extension. First of all, you should configure tls configuration bucket. To trust all certificates: @@ -2101,7 +2100,7 @@ While the REST Client extension aims to be a drop-in replacement for the RESTEas and limitations: - the default scope of the client for the new extension is `@ApplicationScoped` while the `quarkus-resteasy-client` defaults to `@Dependent` -To change this behavior, set the `quarkus.rest-client-reactive.scope` property to the fully qualified scope name. +To change this behavior, set the `quarkus.rest-client.scope` property to the fully qualified scope name. - it is not possible to set `SSLContext` - a few things that don't make sense for a non-blocking implementations, such as setting the `ExecutorService`, don't work