Re: uh oh -- halp!

• Mail folder: WWW Talk Jul-Oct 1993
• Next message: Marc Andreessen: "favor in ny/nyc?"
• Previous message: Richard Wiggins: "Re: Crawling info displays and slide shows"

Errors-To: sanders@bsdi.com
Errors-To: sanders@bsdi.com
Message-id: <9309280505.AA12173@austin.BSDI.COM>
To: www-talk@nxoc01.cern.ch
Subject: Re: uh oh -- halp! 
In-Reply-To: Your message of Mon, 27 Sep 93 21:18:45 CDT.
Errors-To: sanders@bsdi.com
Reply-To: sanders@bsdi.com
Organization: Berkeley Software Design, Inc.
Date: Tue, 28 Sep 1993 00:05:43 -0500
From: Tony Sanders <sanders@bsdi.com>

> 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...

Ok, it's ECONNRESET then.  I just got my signals crossed.  You get the
basic idea anyway :-)  Watch out for SIGPIPE also.  You can get this if
the client is still sending data after the server has already closed.

--sanders