From: "Kristofer T. Karas" <ktk@bigfoot.com>
To: rpjday <rpjday@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is 2.4.15 really available at www.kernel.org?
Date: Fri, 23 Nov 2001 15:28:25 -0500 [thread overview]
Message-ID: <3BFEB169.3E4952A8@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111230437180.7283-100000@localhost.localdomain>
rpjday wrote:
> [...]www.kernel.org/pub/linux/kernel/v2.4/linux-2.4.15.tar.bz2, and it
> completed after downloading *exactly* 155312 bytes, just as before.
>
> getting it via ftp works fine -- it's http that's giving me this
> weird problem. is it just me?
You probably have a proxy server in your path that doesn't re-request partially-sent
files. I have your problem too, using squid-cache as the proxy. Here's what
happens:
The http server (kernel.org) sends the file to the proxy, which sends it to you. But
because the net connection from kernel.org to the proxy is faster than it is from
proxy to you, the tcp window between proxy and kernel.org goes to zero. When it
opens up again, kernel.org closes the connection even though the file is only
partially received. The proxy, failing to detect that the file is smaller than the
Content-Length header said it would be, simply sends the truncated contents your
way.
I "fixed" this bug by using 'wget' to retrieve the files for me. It has the same
problem, obtaining a truncated file; but it is smart enough to re-request missing
byte-ranges of the file, ultimately obtaining the entire thing.
Kris
prev parent reply other threads:[~2001-11-23 20:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-23 8:58 is 2.4.15 really available at www.kernel.org? rpjday
2001-11-23 9:28 ` Keith Owens
2001-11-23 9:41 ` rpjday
2001-11-23 9:43 ` Jochen Striepe
2001-11-23 9:48 ` Rik van Riel
2001-11-23 10:00 ` Oliver.Neukum
2001-11-25 0:41 ` Cameron Simpson
2001-11-23 10:33 ` Flavio Stanchina
2001-11-23 16:05 ` Michael H. Warfield
2001-11-23 16:27 ` Jeff Garzik
2001-11-23 17:25 ` Michael H. Warfield
2001-11-23 19:19 ` Stephen Frost
2001-11-23 20:00 ` J Sloan
2001-11-23 21:08 ` Mike Fedyk
2001-11-23 23:54 ` Michael H. Warfield
2001-11-24 10:01 ` Kai Henningsen
2001-11-24 13:35 ` Keith Owens
2001-11-24 13:56 ` Christoph Hellwig
2001-11-24 22:29 ` H. Peter Anvin
2001-11-24 23:57 ` Keith Owens
2001-11-25 9:59 ` Kai Henningsen
2001-11-25 10:15 ` Mike Fedyk
2001-11-23 9:46 ` Christian Haugan Toldnes
2001-11-23 10:27 ` rpjday
2001-11-23 12:32 ` Stefan Smietanowski
2001-11-23 13:30 ` rpjday
2001-11-23 15:51 ` kees
2001-11-23 16:37 ` Michael H. Warfield
2001-11-23 20:10 ` Ross Vandegrift
2001-11-24 1:14 ` H. Peter Anvin
2001-11-23 20:28 ` Kristofer T. Karas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BFEB169.3E4952A8@bigfoot.com \
--to=ktk@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox