[
https://issues.apache.org/jira/browse/CAMEL-26508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-26508.
---------------------------------
Resolution: Fixed
Fixed by https://github.com/apache/camel/pull/28991 (merged to main as
31afb62070f07ee8240914ad8e70c742a8a220dc).
_Claude Code on behalf of Claus Ibsen (davsclaus)_
> camel-netty - with transferExchange the consumer keeps its own connection
> headers
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-26508
> URL: https://issues.apache.org/jira/browse/CAMEL-26508
> Project: Camel
> Issue Type: Improvement
> Components: camel-netty
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> With transferExchange=true the TCP consumer first sets the headers it derives
> from the connection (CamelNettyRemoteAddress, CamelNettyLocalAddress and,
> with a client certificate, the CamelNettySSLClientCert* headers), and then
> unmarshals the received exchange, which replaces all headers with the ones in
> the transferred exchange.
> The connection headers describe the connection the consumer itself accepted,
> so they should stay the values of the consumer: set them again after the
> exchange is unmarshalled, and do not take CamelNetty* transport headers from
> the transferred exchange. Document this on the transferExchange option.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
