Stefan
The reason to use HTTP 1.0 is that the webservice I'm calling does not
support the chunked encoding style.
If your end server replied with a successful HTTP 200 message for a
chunked encoded HTTP 1.1 request, then that end service and its HTTP
environment does understand chunking perfectly. Looking at the traces,
it seems like its an "Apache-Coyote/1.1" server.. BTW, you did not post
the reply you saw on the TCPMon trace
asankha
Ruwan Linton-3 wrote:
stlecho wrote:
Ruwan,
I've created a Proxy that sends the requests to TCPMon (localhost:8444)
and
here is the result:
POST http://localhost:8444 HTTP/1.1
host: localhost:9444
SOAPAction: urn://fsb.belgium.be/fphp/v3_0/findPerson
Content-Type: text/xml; charset=UTF-8
Transfer-Encoding: chunked
Connection: Keep-Alive
User-Agent: Synapse-HttpComponents-NIO
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user