On Fri, 16 Feb 2001 21:07:22 +0100, Bernie <[EMAIL PROTECTED]> wrote:
> Clarence wrote:
>> I know that you have been paying attention, so I also know YOU know
>> about .ZBMs. And I understand that you would not consider it to be more
>> than a toy, due to it's lack of universal built-in-ness.
> Why don't we just add gziped support to Arachne? Then good servers (Apache
> for instance) will compress the file (atleast I assume that's what it does)
> and send it to the browser for decompression. BMP files should be
> compressed almost as good with gzip as with pkzip and it is a lot easier.
> Still it will not help the poor bastards that don't have such support (both
> NS and IE has it since a few versions back IIRC).
> //Bernie
How would we do that on the server end?
Give the file a name like "testfile.bmp.gz" ???
If so, what content-type do we need to add to Arachne?
Ahhh, there it is... "application/x-gzip"
(according to http://www.ltsw.se/knbase/internet/application.htp )
Now the problem will be getting the servers on the net to conform to it.
(this one does not.... http://support.serv.ch/freebsd/manpages-de/ )
Every .gz file is being sent as "application/octet-stream" :(
There we go.
This site http://www.lsp.ups-tlse.fr/Chafai/Fichiers/ uses the following
content types...
( .ps.gz --- application/postscript
( .pdf.gz --- application/pdf
( .tar.gz --- application/x-tar
However, for each one of these it also sends "content-encoding: x-gzip"
A further check at http://support.serv.ch/freebsd/manpages-de/ shows
that it is also sending "content-encoding: x-gzip"
So if I understand correctly, what Arachne would need to do is to
disregard "content-type" when "content-encoding" is sent.
--
Glenn
http://arachne.cz/
http://freedos-32.sourceforge.net/
http://www.delorie.com/listserv/mime/
http://www.angelfire.com/id/glenndoom/download.htm
