Hello Chris, that server is not only sending the headers last. It is sending the whole head section of the HTTP response after the body. That is not HTTP at all. Not even close. Even though the supposed body is listed in the output as "headers", that's not what HttpClient makes of it. HttpClient simply skips garbage lines at the beginning of a response, until it finds the line starting with "HTTP/1.1". Then, it reads in the head section. And then, it would try to read the body, except that there is none. There is not even the required empty line that terminates the head section.
I have two explanations for this. One: the server is using persistent connections, but gets confused by something the client does. That could happen if you use the SimpleHttpConnectionManager from multiple threads. But if that log is the full log of a test run, that's not what happens. Two: the server is totally screwed and has no idea of what HTTP specifies. In that case, you're best off by connecting directly to the server using a Socket. I'm sorry, but that behavior is way too far off to tweak HttpClient into tolerance. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
