Re: soap post and http 1.1 100 continue

Yep, know that one, Why it does happen: although the HTTP 1.1 spec states that a HTTP 100 SHOULD NOT (or was it MUST NOT ;-) to the client, unless it requires it by a specific header, IIS does it with webservices and thereby about any that are published and maintained with .NET ;-) Solution: A HTTP 100 basically states: "ok I am ready for your content now". You have probably submitted your content already... resend it, but the content only, without the \r\n\r\n mark that separates headers from payload with HTTP. To serve a clean solution you should however go ahead and implement a listener that tries to hear a HTTP 100. With PHP this is kind of tiresome. In my implementation I also just resend the payload ;-) "Davide" <info@dgline.it> schrieb im Newsbeitrag news:20021212171606.46527.qmail@pb1.pair.com... > Hello all > > hope this is the right place to post my question > > this is the situation... > > a soap file sintactically correct... > like this one (plus correct headers..) > > POST /URL HTTP/1.1 > Host: SERVERNAME > Content-Type: text/xml; charset=utf-8 > Content-Length: 520 > Connection: close > SOAPAction: "URL2" > > <?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:Header> > <Authentication > xmlns="http://www.betinternet.com/Events"> > <User>USER</User> > <Password>PASS</Password> > </Authentication> > </soap:Header> > <soap:Body> > <Sports xmlns="URL3" /> > </soap:Body> > </soap:Envelope> > > > i open a socket with the server > post all the above and then wait for server response... > > well > > i receive ONLY > > these 3 lines... > HTTP/1.1 100 Continue > Server: Microsoft-IIS/5.0 > Date: Thu, 12 Dec 2002 17:03:01 GMT > > Well i read a lot of docs about these and found that > Continue is a HTTP 1.1 implementation (a sort of "please wait" usefull in > case of slow connections) > > but after that the php script loops without ending... > > i tested really all the solutions i found on the net plus newsgroup, and > newsletter... > > i tried using curl, libcurl, soap, socket, php and also perl and i got the > same 3 HTTP 1.0 continue and nothing else... > > I tried also posting 1st headers and then the soap envelope but i receive > the same HTTP 1.0 continue... > > But if i make a simple telnet server 80 and post the above it works great... > > so i think it is a sort of limit of the socket reading routine or something > similar... > or may be a little bug or something like that.... > (i have the same problem with visual basic but i solved with a simple wait > for 5 seconds before reading the response...) > > Anyone of u got the same problem? > > Thx in advance and sorry for my bad english :) > > Davide > > > > > > > > >