This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch camel-2.23.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-2.23.x by this push:
new d53c787 Regen
d53c787 is described below
commit d53c787018200732ad42dd94d912e20f1104c738
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Tue Jul 23 10:04:45 2019 +0200
Regen
---
components/camel-ahc/src/main/docs/ahc-component.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/components/camel-ahc/src/main/docs/ahc-component.adoc
b/components/camel-ahc/src/main/docs/ahc-component.adoc
index 64ad05e..0f2759d 100644
--- a/components/camel-ahc/src/main/docs/ahc-component.adoc
+++ b/components/camel-ahc/src/main/docs/ahc-component.adoc
@@ -72,7 +72,7 @@ with the following path and query parameters:
| *bridgeEndpoint* (producer) | If the option is true, then the
Exchange.HTTP_URI header is ignored, and use the endpoint's URI for request.
You may also set the throwExceptionOnFailure to be false to let the AhcProducer
send all the fault response back. | false | boolean
| *bufferSize* (producer) | The initial in-memory buffer size used when
transferring data between Camel and AHC Client. | 4096 | int
| *connectionClose* (producer) | Define if the Connection Close header has to
be added to HTTP Request. This parameter is false by default | false | boolean
-| *cookieHandler* (producer) | Configure a cookie handler to maintain a HTTP
session. If this parameter is defined together with the clientConfig parameter,
make sure that the latter does not contain a cookie handler. | | CookieHandler
+| *cookieHandler* (producer) | Configure a cookie handler to maintain a HTTP
session | | CookieHandler
| *headerFilterStrategy* (producer) | To use a custom HeaderFilterStrategy to
filter header to and from Camel message. | | HeaderFilterStrategy
| *throwExceptionOnFailure* (producer) | Option to disable throwing the
AhcOperationFailedException in case of failed responses from the remote server.
This allows you to get all responses regardless of the HTTP status code. | true
| boolean
| *transferException* (producer) | If enabled and an Exchange failed
processing on the consumer side, and if the caused Exception was send back
serialized in the response as a application/x-java-serialized-object content
type (for example using Jetty or Servlet Camel components). On the producer
side the exception will be deserialized and thrown as is, instead of the
AhcOperationFailedException. The caused exception is required to be serialized.
This is by default turned off. If you enab [...]
