Hi,

Currently, the camel-rabbitmq endpoints, if set as "bridgeEndpoint",
ignores the following exchange's headers : EXCHANGE_NAME & ROUTING_KEY, but
it keeps the previous headers setted, which leak information about the
origin of the event. For example, if my message comes from Exchange A, I
transform it and send it to Exchange B, the RabbitMQProducer will ignore
the headers set by A but still will send them to B, which could leaks some
internal info of A to the consumer of B.

Wouldn't it be more correct to replace those two headers, if we ignore them
? I can do the pull request, but I would like to discuss the idea before.

See RabbitMQProducer:processInOut and processInOnly for related code.

Reply via email to