On Sun, 1 Dec 2002 16:09:22 -0500 (EST), Gregor Jones wrote: > On Sat, 30 Nov 2002, Glenn McCorkle wrote:
>> On Fri, 29 Nov 2002 19:38:30 -0500 (EST), I wrote: >> > On Fri, 29 Nov 2002, Glenn McCorkle wrote: >> >> The correct size of the file is 1,039,025 bytes. >> >> This lets you know that if the file you got is less than that size. >> >> The download is incomplete and you must do it again. >> > Errr, no, you managed to confuse a lot of software by creating a gzipped >> > file that had the wrong file extension on it. Seems like most software >> > detected it as a gzipped file, but only some automatically gunzipped it, >> > and did it without asking. >> I did not create a Gzipped file. >> The file on the site IS a Dos executable. > [snip] > Glenn, my apologies for intemperate criticism based on my > misunderstandings and lack of knowledge (and an apology for my late > apologies, been away from my computers for a couple of days). I must also apologize for getting "snippy" in my replies. Actually, for a while there I was beginning to think that was going nuts. And that I had done the Gzipping but had forgotten doing it. ;-) Well.... thank goodness that I'm not actually any more 'nuts' than I already was to begin with. ;-) And thank you very much for these links. (tray are now saved to disk for future reference) :)) > I just read through all the mail on this and decided I needed to find out > more. A Google search on "Apache compression" turns up this page: > http://www.innerjoin.org/apache-compression/howto.html > where there is a link to > http://www.innerjoin.org/apache-compression/index.html > I quote from the latter page: > "Many browsers can accept gzip compressed data, uncompress it and display > it. Apache can, with various modules, compress data as it is served or > read compressed files from disc and uncompress if it is necessary." > So, it is the server that is doing the compressing. Now, whether the > server at your end is misconfigured or there is something else going I do > not know. On the first of the pages mentioned above, there is a lot of > detail about the compression modes, and HTTP headers and other stuff. It > seems that all this is a WWW consortium standard, though not part of the > RFC standards. > Unfortunately, I cannot take this up again for a few days. Have a couple > of urgent tasks here at the University to deal with. > Perhaps somebody else listening in can look at what the Angelfire server > is doing with HTTP 1.1 requests. > Later > -- > Gregor J Jones mailto:[EMAIL PROTECTED] > Boston MA -- Glenn http://arachne.cz/ http://www.delorie.com/listserv/mime/ http://www.angelfire.com/id/glenndoom/download.htm http://www.thispagecannotbedisplayed.com/