[
https://issues.apache.org/jira/browse/SYNAPSE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305655#comment-15305655
]
Hudson commented on SYNAPSE-923:
--------------------------------
SUCCESS: Integrated in Synapse - Trunk #5247 (See
[https://builds.apache.org/job/Synapse%20-%20Trunk/5247/])
Fixing the support for FORCE_HTTP_CONTENT_LENGTH and
COPY_CONTENT_LENGTH_FROM_INCOMING; Applying the patch from SYNAPSE-923
(hiranya: rev 1745938)
*
java/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/ClientWorker.java
*
java/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/PassThroughConstants.java
*
java/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/PassThroughHttpSender.java
*
java/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/ServerWorker.java
*
java/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/TargetRequest.java
*
java/modules/transports/core/nhttp/src/main/java/org/apache/synapse/transport/passthru/util/SourceResponseFactory.java
> FORCE_HTTP_CONTENT_LENGTH /COPY_CONTENT_LENGTH_FROM_INCOMING Has been broken
> in PT
> ----------------------------------------------------------------------------------
>
> Key: SYNAPSE-923
> URL: https://issues.apache.org/jira/browse/SYNAPSE-923
> Project: Synapse
> Issue Type: Improvement
> Components: Transports
> Affects Versions: FUTURE
> Environment: Ubuntu 12.04
> Reporter: Dushan Sachinda Abeyruwan
> Assignee: Hiranya Jayathilaka
> Priority: Blocker
> Fix For: FUTURE
>
> Attachments: SYNAPSE-923.diff, passthrough_force_content.txt
>
>
> ESB handles its responses chunk manner, there is a situation where if the we
> are passthough any given request but the backend does not support chunk, in
> that case if
> <property name="FORCE_HTTP_CONTENT_LENGTH" value="true"
> scope="axis2"/>
> <property name="COPY_CONTENT_LENGTH_FROM_INCOMING" value="true"
> scope="axis2"/>
> defines in Synapse configuration in the OUT or IN path, we should not
> required to build the given message to calculate its content length, its a
> adding overhead, so the given implementation simply added the content length
> instead of chunking.
> Sample configuration
> <proxy xmlns="http://ws.apache.org/ns/synapse"; name="ContentProxy"
> transports="https,http" statistics="disable" trace="disable"
> startOnLoad="true">
> <target>
> <inSequence>
> <property name="FORCE_HTTP_CONTENT_LENGTH" value="true"
> scope="axis2"/>
> <property name="COPY_CONTENT_LENGTH_FROM_INCOMING" value="true"
> scope="axis2"/>
> </inSequence>
> <outSequence>
> <property name="FORCE_HTTP_CONTENT_LENGTH" value="true"
> scope="axis2"/>
> <property name="COPY_CONTENT_LENGTH_FROM_INCOMING" value="true"
> scope="axis2"/>
> <send/>
> </outSequence>
> <endpoint>
> <address uri="http://localhost:8091/wso2loadtest/120k/"/>
> </endpoint>
> </target>
> <description></description>
> </proxy>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org
For additional commands, e-mail: dev-h...@synapse.apache.org
