Rob van der Heij wrote:
On Mon, Apr 21, 2008 at 11:50 PM, Paul Gilmartin wrote:
Here's my problematic code. I tried to obscure local
server names. That merely means I don't trust our firewall.
It looks like you treat a line with just CRLF as end of the body. It
is my understanding that with HTTP/1.0 only the peer closing the
connection indicates the end of the body. And when you leave that loop
early you probably are unable to terminate the tcpclient in the
addpipe (you probably also need to sever the added input to avoid
tcpclient waiting to get rid of the data after that null line).
I thought I had done the CRLF right. Now I need to look at
my own code to verify. In any case, that sort of coding
error should be data-sensitive and reproducible, whereas the
failure I'm experiencing is intermittent.
But it's possible that in its lifetime it has never encountered
CRLFCRLF, which I assume would be needed to trigger the failure
you envision.
I'm looking at WGET. Is it proxy-able? And I see:
'| h: httpsplit', /* Split header and body */
'| xlate from 850 to 1047', /* ASCII to EBCDIC */
Does that mean it always translates the body to EBCDIC?
I'll need binary.
Thanks,
gil
