I don't know if this might be relevant, but... Some years ago I had problems with a CMS http client when talking to a specific server, which in that case was on OS/400, but there might be something in common. After sending the request, something equivalent to the TCP/IP equivalent of EOF was being sent shortly afterwards (this was triggered by TCPCLIEN reaching EOF on its input stream). On receiving the request, the server started sending the response, but when it received the "EOF" it hung or closed the connection, so small responses worked, but larger responses usually failed. This was later identified as a bug in the server, which should not have been treating the EOF as an attempt to stop the response.
The solution in that case was to defer sending the EOF until the complete response had been received. The WW2GET EXEC which I've included with the Charlotte browser includes that fix if you have a copy dated 2003-05-07 or later. Jonathan Scott IBM Hursley, UK
