How to handle a "100 continue" http_post responce

hi ,
i’m using an http post command to send data to a webservice (the data is formatted as a SOAP message),
each time i sent the message to the web service i receive the the RESPONCE “100 Continue” wich means that all other data will arrive in anothe message from the server.
instead ,after data trasmission i receive WIP_CEV_PEER_CLOSE containig the “100 continue” answare and no other events.

testing the same message with “fiddler” , i receice a correct- complete response .
tracing exchanged messages on the server side , it seems that wip , after the 100 continue message , is not able to complete correctly the message exchange sequence .

does any one know how to solve this problem?
thanks for your help

here is a trace as example

[]: initialized.

GPRS: open: -> DISCONNECTED
GPRS: start: -> CONNECTING
GPRS: GPRS EVENT SETUP OK (cid=1): GPRS activate
GPRS: GPRS EVENT: 27 (cid=1)

+WIND: 15,3,"+08",4,“09/07/28,07:28:00+08”,6,“1”
GPRS: GPRS EVENT ACTIVATE OK (cid=1): FCM open
GPRS: FCM subscribe: 0
GPRS: FCM EVENT FLOW OPENNED: -> CONNECTED

HTTP Client Service test application : Init

HTTP STRSOAP : Init
[HTTP] new request GET sitecsrl.eu/wbsSitecTest/service1.asmx?wsdl HTTP/1.1 @ 01d10f0a
[HTTP] req parsed URL: /wbsSitecTest/service1.asmx?wsdl at www.sitecsrl.eu
[HTTP] connect to host: www.sitecsrl.eu:80
http_ClientTestDataHandler: Start

http_ClientTestDataHandler: WIP_CEV_WRITE

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=“http://www.w3.org/2001/XMLSchema” xmlns:soap=“http://schemas.xmlsoap.org/soap/envelope/”>
soap:Body

stringa_di_brea

</soap:Body>
</soap:Envelope>

http_ClientTestDataHandler: WIP_CEV_WRITE_end

http_ClientTestDataHandler: Done
http_ClientTestDataHandler: Status=100
http_ClientTestDataHandler: Reason=“Continue”
[WIP] closing HTTP_DATA 0x1d10f0a
[HTTP] destroy request @ 01d10f0a
[WIP] closing TCPCLIENT 0x1d113ae

Hi

Was this issue ever resolved?

I am doing SOAP over HTTP now as well.