Comment 4 for bug 704015

The problem that I reproduced (or "reproduced") using truncate(1) turned out not to have anything with the client at all. If the file is truncated, the DiskFile in object server reaches EOF, and quits. The proxy server does nothing about it either. However, the client does not know that there was an EOF, so it just sits there. Meanwhile, servers keep their connections open and cached, and so we just hung. In theory, there should be a timeout on an idle connection, but it does not happen. No matter, object server has to signal the premature EOF, and proxy server has to pass it to client. And the only way to do it in HTTP is to break the TCP connection.