[
https://issues.apache.org/jira/browse/SYNAPSE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707828#action_12707828
]
Ruwan Linton commented on SYNAPSE-525:
--------------------------------------
I will definitely have a look at these issues... but the rationale behind this
was to make the addresing handling be consistent with other QoS handlings like
security and reliable messaging. In those cases if you want to drop them, you
need to drop them within the configuration, but if you do not specify anything
in the configuration we are preserving the security and RM headers. We need to
be consistent about these and I didn't want to specialize the addressing
scenario.
I still believe that preserving addressing is the correct behavior.... please
note that options cloning is not related to the preserving addressing headers,
which also seems to be introducing a quite a bit of issues.
I will have a look at all the samples and these changes once I get some free
slot.
> Option to preserve addressing headers should be available
> ---------------------------------------------------------
>
> Key: SYNAPSE-525
> URL: https://issues.apache.org/jira/browse/SYNAPSE-525
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2
> Environment: all env
> Reporter: Ruwan Linton
> Assignee: Ruwan Linton
> Fix For: 1.3
>
>
> For the moment Synapse replaces all the addressing headers when sending the
> message out to the routed service, but there can be case where the mediation
> configuration should preserve the addressing headers. For example like
> wsa:Reply-To
> So this requires a switch to configure the send mediator to not to alter
> addressing headers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
