Date: Thu, 24 Jul 1997 02:55:53 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru> To: Marc Slemko <marcs@znep.com> 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.96.970724025336.5476A-100000@lsd.relcom.eu.net> In-Reply-To: <Pine.BSF.3.95.970723163735.28563C-100000@alive.znep.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Jul 1997, Marc Slemko wrote: > 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. I disable both rfc1323 and rfc1644 and it still not work (is it work for you?) > 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. I agree. Any objection to revert it to HTTP/1.0? > > > > fetch http://www.lothlorien.net/~squirrel/giger/art/Necronomicon_I.jpg > > > > > > > always says "connection reset by peer" in the middle of file transfer, -- 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.96.970724025336.5476A-100000>