[ http://wso2.org/jira/browse/ESBJAVA-415?page=all ]
Asankha Perera resolved ESBJAVA-415.
------------------------------------
Resolution: Invalid
Since chunked encoding is more efficient and does not require the sender to
compute the length of the full payload by buffering it in memory first, the ESB
tries to use HTTP 1.1 by default. This is done irrespective of the fact that
the request may have used Content-Length header.. well it may have come over
JMS or even VFS anyway!.. so unless you ask the ESB to use HTTP 1.0 for
outgoing requests, we will default to using HTTP 1.1
You could use the following property to force the use of HTTP 1.0 for outgoing
requests
<property name="FORCE_HTTP_1.0" value="true" scope="axis2-client"/>
Now if you do a trace, you will notice for example that a previous:
POST http://localhost:9001/soap/SimpleStockQuoteService HTTP/1.1
Host: 127.0.0.1
SOAPAction: urn:getQuote
Content-Type: text/xml; charset=UTF-8
Transfer-Encoding: chunked
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO
has changed to:
POST http://localhost:9001/soap/SimpleStockQuoteService HTTP/1.0
Host: 127.0.0.1
SOAPAction: urn:getQuote
Content-Type: text/xml; charset=UTF-8
Content-Length: 328
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO
> When sending SOAP requests to HTTP endpoints, the Content-Length header is
> not sent, even if the original request has it
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-415
> URL: http://wso2.org/jira/browse/ESBJAVA-415
> Project: WSO2 ESB
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: 1.5
> Environment: Windows, wso2esb 1.5 release
> Reporter: Alex Reis
> Assigned To: Asankha Perera
>
> Whenever I try to proxy the Progress OpenEdge WebServices Adapter services
> within the ESB and invoke it, I
> get the response Error in SOAP Envelope: Content length must be specified.
> (10913).
> If I invoke it directly through soapUI, it works AS LONG as I provide
> the Content-Length header manually.
> So what I need to do is setup an input sequence that adds the
> Content-Length headers with the payload + soap headers size. I tried
> using the Header mediator but it only adds the SOAP headers, not HTTP.
> There should be a way to do this in Synapse/WSO2 ESB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
