Garret Wilson wrote:
So this is getting stranger.
Just to preclude any error on my part, I did a simple loop that output
every character received from the response. The HTTP response status
line and headers come down fine, including the CRLF that separates the
headers from the body. And
Wade Chandler wrote:
Garret Wilson wrote:
So this is getting stranger.
Just to preclude any error on my part, I did a simple loop that output
every character received from the response. The HTTP response status
line and headers come down fine, including the CRLF that separates the
headers from
Wade Chandler wrote:
Wade Chandler wrote:
Garret Wilson wrote:
So this is getting stranger.
Just to preclude any error on my part, I did a simple loop that
output every character received from the response. The HTTP response
status line and headers come down fine, including the CRLF that
Wade Chandler wrote:
Actually what is happening is this You are using a buffered stream.
It is reading past the amount returnedand then the tcp/ip socket is
blocking because you have it open as a keep alive. You have to only
read the number of bytes available and not keep trying to
