synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] [Commented] (SYNAPSE-913) Pass Through HTTP Transport for Synapse and Using the Pass Through Transport by Default
Date Wed, 03 Oct 2012 13:40:08 GMT


Amila Chinthaka Suriarachchi commented on SYNAPSE-913:

the problem is like this.

This client sends the content length header. and synapse pass through just copy the same content
length header to BE. so that is wrong when doing an xslt. 

I added the content length to remove headers in

if (HTTP.CONN_DIRECTIVE.equalsIgnoreCase(headerName) ||
                HTTP.TRANSFER_ENCODING.equalsIgnoreCase(headerName) ||
                HTTP.DATE_HEADER.equalsIgnoreCase(headerName) ||
                HTTP.CONTENT_LEN.equalsIgnoreCase(headerName) ||
                HTTP.CONN_KEEP_ALIVE.equalsIgnoreCase(headerName)) {

then that was fine. 
> Pass Through HTTP Transport for Synapse and Using the Pass Through Transport by Default
> ---------------------------------------------------------------------------------------
>                 Key: SYNAPSE-913
>                 URL:
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core, Transports
>         Environment: Any
>            Reporter: Hiranya Jayathilaka
>             Fix For: FUTURE
>         Attachments: SYNAPSE_PASS_THRU_8.patch
> This improvement has 2 main aspects:
> 1. Contributing the pass through HTTP transport developed at WSO2 to Synapse
> 2. Modifying Synapse to use the pass through HTTP transport as the default (this requires
some minor changes to the transport too)
> The pass through transport, as it stands now, can only be used for simple pass through,
static routing and header based routing scenarios. It cannot be used for any scenario where
content lookup or manipulation is required. This effort makes the pass through transport one
of the core transports of Synapse, and modifies Synapse and the transport in a way so that
the transport can be used in any scenario without restrictions.
> See the conversations at:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message