Monday, May 14, 2001 03:02 PM
I've seen this problem a lot of times and I've run this problem on manu newsgroup too, obtaining always the same answer: it looks like something that you can ignore.
It seems that this exception it's thrown when, for example, you are requesting an object (page, image, etc.) and before completing the reception of it, the stream between the client and the server is interrupted or closed, maybe because of a "stop" pressed or a new request.
I've even thought that this could be caused when the Content-Length of an object it's not specified and the connection it's not closed in a "clean" way when the object it's completed.
Again, I've started ignore it.