[
https://issues.apache.org/jira/browse/SYNAPSE-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748238#action_12748238
]
Ruwan Linton commented on SYNAPSE-549:
--------------------------------------
Also, if this is working for addressing as well correctly we should be able to
get rid of the removeAddresingHeaders internal method that is invoked before
sending...
> Implement a smarter default policy for SOAP header removal/preservation
> -----------------------------------------------------------------------
>
> Key: SYNAPSE-549
> URL: https://issues.apache.org/jira/browse/SYNAPSE-549
> Project: Synapse
> Issue Type: Improvement
> Components: Proxy Services
> Reporter: Andreas Veithen
> Priority: Minor
> Fix For: 1.3.1
>
> Attachments: synapse-549.patch
>
>
> Currently, when sending a message out to the target service, by default the
> WS-Addressing headers are removed while all other headers are preserved.
> SYNAPSE-525 introduced the option to preserve WS-Addressing headers.
> The most reasonable default behavior would actually be as follows:
> - If the SOAP header has been processed by a module engaged on the proxy
> service, remove it when forwarding the message.
> - If the SOAP header has not been processed by a module engaged on the proxy
> service, preserve it and forward it to the target service.
> Note that since only addressing is engaged by default on proxy services, the
> current behavior is consistent with this default policy, except when security
> or RM is enabled. In those latter cases, samples 200 and 201 clearly show
> that the proposed behavior would be much more natural.
> We should also apply a similar default policy to responses sent back to the
> client:
> - If the SOAP header has been processed by a module engaged by
> Axis2FlexibleMEPClient, remove it when sending back the response.
> - If the SOAP header has not been processed by a module engaged by
> Axis2FlexibleMEPClient, preserve it.
> For this case, samples 100 and 101 are interesting.
> Note that since Axis2 keeps track of processed headers using the
> setProcessed/isProcessed methods in SOAPHeaderBlock, the proposed change
> could be implemented in a completely generic way.
> Since there will be cases where the proposed default policy is not
> appropriate, we should also add a generic mechanism to preserve/remove
> specific 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: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
