in reply to Socket stops at Header not handling Continuation

By "Continuation" I assume you mean HTTP's "100 Continue" feature, as documented in the HTTP RFC.

If the client has "Expect: 100-continue" as one if its request headers, then try replying "100 (Continue)\r\n" when you see the blank header (i.e. "\r\n\r\n"). The client should then send the body of the request. After you've received that, then you send the final response as normal.

Replies are listed 'Best First'.
Re: Re: Socket stops at Header not handling Continuation
by dwatson06 (Friar) on May 10, 2004 at 14:06 UTC
    Thanks for the Response Duco, I have tried that as 100-continue, 100 (Continue) and several other ways listed on the net...
    The body is coming in, I can see it in the packet sniffer. It is an XML file that I must parse and return a result from. Just before the XML file coming in is some strange characters (...+......._..E...i.@...). After that the xml files displays.
    Could there be a conflict here? Is there a way to strip this?