[
https://issues.apache.org/jira/browse/SYNAPSE-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934217#action_12934217
]
Ruwan Linton commented on SYNAPSE-693:
--------------------------------------
This has been introduced with a change that we have done to remove the
processed headers before sending the message out. There is a property to
control that behavior though, so this comes down to a configuration error,
where we need to specifically ask to keep the processed headers.
We are talking about backwards incompatibilities and this is a dangerous form
of the backward incompatibility, where it seems to work but with a completely
different behavior. :-( So whether we agree or not 2.0 differs from many ways
to 1.x
BTW: I have fixed the issue by adding the property to the sample configuration
:-)
> Sample 153 is Broken
> --------------------
>
> Key: SYNAPSE-693
> URL: https://issues.apache.org/jira/browse/SYNAPSE-693
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0
> Reporter: Hiranya Jayathilaka
> Assignee: Ruwan Linton
> Priority: Blocker
> Fix For: 2.0
>
>
> Sample 153 doesn't work as expected. Synapse is supposed to get the secured
> message and route it to the backend service as it is. But it removes the
> security headers during the process. Hence the request fails at the backend
> server.
--
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: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
