Created by (tenthumbs@cybernex.net) on Saturday, May 9, 1998 10:12:47 AM PDT Additional Details : If the browser reuses a cached socket and the socket closes unexpectedly, net_parse_first_http_line returns the "Document contains no data" error. If the browser knows how long the socket will remain available, it should respect that. If the socket doesn't know, it should not just give up but rather try a news socket. I have more data available.

Judson for comments.

tenthumbs, Do you have a reproducible test case? I've looked at the code paths and am not seeing how this behavior can happen. If the connection came from the cache and the read fails as a result of the socket closing, we'll try again, opening another socket in the process.

Ah, old bug. This problem disappeared a few months ago.

Marking Verified/Invalid.