[ 
https://issues.apache.org/jira/browse/AXIS2-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Heshan Suriyaarachchi updated AXIS2-5024:
-----------------------------------------

    Attachment: synapse-local-transport-transport-header-verification.xml

Hi Andreas, 

I am attaching a Synapse configuration to demonstrate what I am trying to 
achieve here. In this scenario, I am using local transport to communicate 
between Apache Synapse proxy services. First the LocalTransportProxy is called 
and it calls the Second proxy through the local transport. Then the SecondProxy 
calls the StockQuoteProxy via the local transport. 

LocalTransportProxy ---local transport---> SecondProxy ---local transport---> 
StockQuoteProxy

With the current implementation of the local transport, if transport header is 
set at the LocalTransportProxy, it is not propagated to the SecondProxy. 
eg. : I am setting a transport header named header1 with value1 but it is not 
there, when I try to log the transport header1's value at the SecondProxy.

The patch attacted earlier fixes this issue. 

> Issue in setting transport headers in Axis2 local transport
> -----------------------------------------------------------
>
>                 Key: AXIS2-5024
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5024
>             Project: Axis2
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.5.4
>            Reporter: Heshan Suriyaarachchi
>             Fix For: 1.6.0, nightly
>
>         Attachments: AXIS2-5024-patch.diff, 
> synapse-local-transport-transport-header-verification.xml
>
>
> Transport headers are not properly set in the Axis2 local transport. 
> Therefore, already set transport headers are not propagated correctly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to