This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new 0491209 Regen
0491209 is described below
commit 0491209dabedd1e11266a9a737ceb0d360f0a2f2
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Sun Nov 24 11:30:31 2019 +0100
Regen
---
components/camel-netty-http/src/main/docs/netty-http-component.adoc | 3 ++-
.../camel-platform-http/src/main/docs/platform-http-component.adoc | 3 ++-
docs/components/modules/ROOT/pages/netty-http-component.adoc | 3 ++-
docs/components/modules/ROOT/pages/platform-http-component.adoc | 3 ++-
4 files changed, 8 insertions(+), 4 deletions(-)
diff --git
a/components/camel-netty-http/src/main/docs/netty-http-component.adoc
b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
index 7a5f668..4465f29 100644
--- a/components/camel-netty-http/src/main/docs/netty-http-component.adoc
+++ b/components/camel-netty-http/src/main/docs/netty-http-component.adoc
@@ -248,7 +248,7 @@ When using Spring Boot make sure to use the following Maven
dependency to have s
----
-The component supports 35 options, which are listed below.
+The component supports 36 options, which are listed below.
@@ -262,6 +262,7 @@ The component supports 35 options, which are listed below.
| *camel.component.netty-http.configuration.compression* | Allow using
gzip/deflate for compression on the Netty HTTP server if the client supports it
from the HTTP headers. | false | Boolean
| *camel.component.netty-http.configuration.disable-stream-cache* | Determines
whether or not the raw input stream from Netty HttpRequest#getContent() or
HttpResponset#getContent() is cached or not (Camel will read the stream into a
in light-weight memory based Stream caching) cache. By default Camel will cache
the Netty input stream to support reading it multiple times to ensure it Camel
can retrieve all data from the stream. However you can set this option to true
when you for example [...]
| *camel.component.netty-http.configuration.host* | The local hostname such as
localhost, or 0.0.0.0 when being a consumer. The remote HTTP server hostname
when using producer. | | String
+| *camel.component.netty-http.configuration.log-warn-on-bad-request* | Whether
Netty HTTP server should log a WARN if decoding the HTTP request failed and a
HTTP Status 400 (bad request) is returned. | true | Boolean
| *camel.component.netty-http.configuration.map-headers* | If this option is
enabled, then during binding from Netty to Camel Message then the headers will
be mapped as well (eg added as header to the Camel Message as well). You can
turn off this option to disable this. The headers can still be accessed from
the org.apache.camel.component.netty.http.NettyHttpMessage message with the
method getHttpRequest() that returns the Netty HTTP request
io.netty.handler.codec.http.HttpRequest instan [...]
| *camel.component.netty-http.configuration.match-on-uri-prefix* | Whether or
not Camel should try to find a target consumer by matching the URI prefix if no
exact match is found. | false | Boolean
| *camel.component.netty-http.configuration.max-header-size* | The maximum
length of all headers. If the sum of the length of each header exceeds this
value, a {@link io.netty.handler.codec.TooLongFrameException} will be raised. |
8192 | Integer
diff --git
a/components/camel-platform-http/src/main/docs/platform-http-component.adoc
b/components/camel-platform-http/src/main/docs/platform-http-component.adoc
index b332653..57eb69c 100644
--- a/components/camel-platform-http/src/main/docs/platform-http-component.adoc
+++ b/components/camel-platform-http/src/main/docs/platform-http-component.adoc
@@ -1,3 +1,4 @@
+[[platform-http-component]]
= Platform HTTP Component
*Since Camel 3.0*
@@ -52,4 +53,4 @@ The component supports 4 options, which are listed below.
| *camel.component.platform-http.enabled* | Whether to enable auto
configuration of the platform-http component. This is enabled by default. | |
Boolean
| *camel.component.platform-http.lazy-start-producer* | Whether the producer
should be started lazy (on the first message). By starting lazy you can use
this to allow CamelContext and routes to startup in situations where a producer
may otherwise fail during starting and cause the route to fail being started.
By deferring this startup to be lazy then the startup failure can be handled
during routing messages via Camel's routing error handlers. Beware that when
the first message is proces [...]
|===
-// spring-boot-auto-configure options: END
+// spring-boot-auto-configure options: END
\ No newline at end of file
diff --git a/docs/components/modules/ROOT/pages/netty-http-component.adoc
b/docs/components/modules/ROOT/pages/netty-http-component.adoc
index b882de2..0068b32 100644
--- a/docs/components/modules/ROOT/pages/netty-http-component.adoc
+++ b/docs/components/modules/ROOT/pages/netty-http-component.adoc
@@ -249,7 +249,7 @@ When using Spring Boot make sure to use the following Maven
dependency to have s
----
-The component supports 35 options, which are listed below.
+The component supports 36 options, which are listed below.
@@ -263,6 +263,7 @@ The component supports 35 options, which are listed below.
| *camel.component.netty-http.configuration.compression* | Allow using
gzip/deflate for compression on the Netty HTTP server if the client supports it
from the HTTP headers. | false | Boolean
| *camel.component.netty-http.configuration.disable-stream-cache* | Determines
whether or not the raw input stream from Netty HttpRequest#getContent() or
HttpResponset#getContent() is cached or not (Camel will read the stream into a
in light-weight memory based Stream caching) cache. By default Camel will cache
the Netty input stream to support reading it multiple times to ensure it Camel
can retrieve all data from the stream. However you can set this option to true
when you for example [...]
| *camel.component.netty-http.configuration.host* | The local hostname such as
localhost, or 0.0.0.0 when being a consumer. The remote HTTP server hostname
when using producer. | | String
+| *camel.component.netty-http.configuration.log-warn-on-bad-request* | Whether
Netty HTTP server should log a WARN if decoding the HTTP request failed and a
HTTP Status 400 (bad request) is returned. | true | Boolean
| *camel.component.netty-http.configuration.map-headers* | If this option is
enabled, then during binding from Netty to Camel Message then the headers will
be mapped as well (eg added as header to the Camel Message as well). You can
turn off this option to disable this. The headers can still be accessed from
the org.apache.camel.component.netty.http.NettyHttpMessage message with the
method getHttpRequest() that returns the Netty HTTP request
io.netty.handler.codec.http.HttpRequest instan [...]
| *camel.component.netty-http.configuration.match-on-uri-prefix* | Whether or
not Camel should try to find a target consumer by matching the URI prefix if no
exact match is found. | false | Boolean
| *camel.component.netty-http.configuration.max-header-size* | The maximum
length of all headers. If the sum of the length of each header exceeds this
value, a {@link io.netty.handler.codec.TooLongFrameException} will be raised. |
8192 | Integer
diff --git a/docs/components/modules/ROOT/pages/platform-http-component.adoc
b/docs/components/modules/ROOT/pages/platform-http-component.adoc
index 1ec4e0c..0bb75b1 100644
--- a/docs/components/modules/ROOT/pages/platform-http-component.adoc
+++ b/docs/components/modules/ROOT/pages/platform-http-component.adoc
@@ -1,3 +1,4 @@
+[[platform-http-component]]
= Platform HTTP Component
:page-source:
components/camel-platform-http/src/main/docs/platform-http-component.adoc
@@ -53,4 +54,4 @@ The component supports 4 options, which are listed below.
| *camel.component.platform-http.enabled* | Whether to enable auto
configuration of the platform-http component. This is enabled by default. | |
Boolean
| *camel.component.platform-http.lazy-start-producer* | Whether the producer
should be started lazy (on the first message). By starting lazy you can use
this to allow CamelContext and routes to startup in situations where a producer
may otherwise fail during starting and cause the route to fail being started.
By deferring this startup to be lazy then the startup failure can be handled
during routing messages via Camel's routing error handlers. Beware that when
the first message is proces [...]
|===
-// spring-boot-auto-configure options: END
+// spring-boot-auto-configure options: END
\ No newline at end of file
