[
https://issues.apache.org/jira/browse/SYNAPSE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700446#action_12700446
]
Andreas Veithen commented on SYNAPSE-525:
-----------------------------------------
The following change in Axis2FlexibleMEPClient causes a serious issue:
- Options clientOptions = new Options();
+ Options clientOptions =
MessageHelper.cloneOptions(originalInMsgCtx.getOptions());
With this change, if the incoming request has no WS-Addressing headers, the
proxy service seems to attempt sending the outgoing message to itself instead
of the target endpoint!
The issue can be reproduced with sample 150: use SOAPUI to send a message
without WS-Addressing to the proxy service. It will fail saying that Axis2
can't infer the outgoing transport. The endpoint URI from which it tries to
infer the transport is the URI of the proxy service, not the target service.
> 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]
