From: "Riley Williams" <Riley@Williams.Name>
To: Bart Oldeman <bartoldeman@users.sourceforge.net>,
Ged Haywood <ged@www2.jubileegroup.co.uk>
Cc: Claudia Neumann <dr.claudia.neumann@gmx.de>,
linux-msdos <linux-msdos@vger.kernel.org>
Subject: RE: Download Problem DOSEMU-1.1.5
Date: Tue, 10 Jun 2003 09:41:02 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAGEEHEEAA.Riley@Williams.Name> (raw)
In-Reply-To: <Pine.LNX.4.44.0306091325460.23596-100000@pg5.enm.bris.ac.uk>
Hi all.
>>> if it is a browser mistake, then Mozilla 1.2.1 has the same problem.
>> It could easily be that, but I still think there's more to it than
>> just the browser. I've used the same browser to download other .tgz
>> files today with no problem.
> right, the problem is with some sourceforge mirrors, see
>
http://sourceforge.net/tracker/?group_id=1&atid=200001&func=detail&aid=74722
9
Based on that webpage, it's happening because the web server is sending
a header that reads...
Content-Encoding: x-gzip
...and the browser is CORRECTLY treating this as a request to decompress
the file on the fly. Basically, it's a web server misconfiguration.
The reason that wget doesn't hit the problem is that it's mirroring the
site, so correctly FAILS to decompress as it assumes your web server is
set up identical to the one it's mirroring.
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 5-Jun-2003
next prev parent reply other threads:[~2003-06-10 8:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 0:07 [ANNOUNCE] DOSEMU-1.1.5 Bart Oldeman
2003-06-07 19:44 ` Download Problem DOSEMU-1.1.5 Claudia Neumann
2003-06-07 22:57 ` Bart Oldeman
2003-06-08 0:05 ` Ged Haywood
2003-06-08 9:28 ` Alistair MacDonald
2003-06-08 9:50 ` Ged Haywood
2003-06-08 10:58 ` Bart Oldeman
2003-06-08 21:40 ` Claudia Neumann
2003-06-08 22:32 ` Ged Haywood
2003-06-09 12:33 ` Bart Oldeman
2003-06-09 14:44 ` Ged Haywood
2003-06-10 8:41 ` Riley Williams [this message]
2003-06-10 8:17 ` Justin Zygmont
2003-06-07 23:19 ` Ross Vandegrift
2003-06-10 20:43 ` DOSEMU-1.1.5 vs. DPMI Peter B. Steiger
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 9:33 Download Problem DOSEMU-1.1.5 Stas Sergeev
2003-06-13 3:17 ` Justin Zygmont
2003-06-14 8:13 ` Ryan Underwood
2003-06-14 16:45 ` Justin Zygmont
2003-06-10 9:37 Stas Sergeev
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=BKEGKPICNAKILKJKMHCAGEEHEEAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=bartoldeman@users.sourceforge.net \
--cc=dr.claudia.neumann@gmx.de \
--cc=ged@www2.jubileegroup.co.uk \
--cc=linux-msdos@vger.kernel.org \
/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