Re: uh oh -- halp!

Marc Andreessen (
Mon, 27 Sep 93 21:18:45 -0500

Tony Sanders writes:
> [problem about supporting HTTP/1.0 and HTTP0 in same client]
> ...
> > > The result is that the socket gets confused and the client only ends
> > > up getting the first chunk of data (usually 1024 bytes).
> I think the client is getting ENOTCONN when the server does the close.
> You could work around this by detecting ENOTCONN and retrying without
> "HTTP/1.0".

As it turns out, this seems to work -- ECONNRESET is the more common
errno in this situation (the one I see) but I'll have Mosaic 2.0 check
for either...