Date: Wed, 23 Jul 1997 16:43:41 -0600 (MDT) From: Marc Slemko <marcs@znep.com> To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, FreeBSD-current <current@FreeBSD.ORG> Subject: Re: 'fetch' error with http, fix wanted Message-ID: <Pine.BSF.3.95.970723163735.28563C-100000@alive.znep.com> In-Reply-To: <Pine.BSF.3.96.970724012403.3952A-100000@lsd.relcom.eu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
It will happen at times if you try to talk to certain boxes with T/TCP like SunOS 4.x boxes. Disable net.inet.tcp.rfc1644 and it should work. You probably only see it with fetch because it appears to be more efficient with the way it sends the headers, so the request goes in a single packet with the SYN. Haven't looked into it further to see who is at fault yet. Oh yes, on a completely unrelated note... fetch is also broken in that it makes HTTP/1.1 requests but doesn't properly deal with the results. This gains it absolutely nothing but hurts a lot in some case. eg. fetch http://www.apache.org/index.html doesn't give the proper output because fetch doesn't know about chunked encoding. It is bogus, both in theory and practice, for fetch to claim to be HTTP/1.1 if it can't handle chunked encodings. On Thu, 24 Jul 1997, [KOI8-R] Андрей Чернов wrote: > On Wed, 23 Jul 1997, Garrett Wollman wrote: > > > <<On Thu, 24 Jul 1997 00:20:20 +0400 (MSD), =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> said: > > > > > This command > > > fetch http://www.lothlorien.net/~squirrel/giger/art/Necronomicon_I.jpg > > > > > always says "connection reset by peer" in the middle of file transfer, > > > meanwhile, new -current ftp or lynx do it sucessfully! > > > Does anybody knows sockets enough to fix it? > > > > I would make a wild guess and suggest that it's likely a TCP bug on > > their end, but without being able to get a tcpdump trace of it I can't > > be certain. (It could, of course, also be a TCP bug on our end.) > > > > But why ftp or lynx always works, if it is TCP bug? They show -stalled- > state sometimes and I think fetch treat -stalled- as resetting by peer... > > I see the same behaviour already 4 times in the past, but forget other > URLs. > > -- > Andrey A. Chernov > <ache@null.net> > http://www.nagual.pp.ru/~ache/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970723163735.28563C-100000>