[camel] 01/02: Camel-Rabbitmq: Added more docs about allowCustomHeaders

[ac...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 7cb89ec6f337580dac123863c4bbddc1953001ed
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Tue Mar 10 12:52:55 2020 +0100

    Camel-Rabbitmq: Added more docs about allowCustomHeaders
---
 .../camel-rabbitmq/src/main/docs/rabbitmq-component.adoc       | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc b/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
index 45f956a..b5a78e1 100644
--- a/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
+++ b/components/camel-rabbitmq/src/main/docs/rabbitmq-component.adoc
@@ -319,6 +319,16 @@ producer will also set the headers for downstream processors once the
 exchange has taken place. Any headers set prior to production that the
 producer sets will be overridden.
 
+== Allowing custom Headers
+
+The `allowCustomHeaders` endpoint option can be used to avoid adding custom headers to the message sent to RabbitMQ.
+If set to false, the user will have only rabbitmq.* headers in the payload of the message. Default value for this option is true.
+
+[NOTE]
+====
+If you decide to use the allowCustomHeaders option, don't add sensitive information as header. It's not recommended and it's dangerous. Don't do it.
+====
+
 == Message Body
 
 The component will use the camel exchange in body as the rabbit mq