On Sat, 26 Feb 2000, Mark Mentovai wrote:
> Try http://lynx.isc.org/current/.
>
> The server running at lynx.isc.org should have some sense knocked into its
> configuration so that it stops sending .bz2 files as text/plain.
Yes, definitely!
All it takes is putting the right stuff in the apache *.conf files or in
.htaccess.
> It should
> either be told that bz2 indicates an x-bzip2 transfer encoding or an
> application/x-bzip2 type. The former is probably preferrable, since Apache
> by default treats things like .gz as a transfer encoding (x-gzip) and not an
> independent MIME type.
I find the latter preferable, as long as there is no official registration
for a bzip2 Content-Encodin (*not* Transfer-Encodfing, that would be
something different). We don't even know what it should say: "x-bzip2",
"x-bunzip2", just "x-bzip", or what? An unrecognized
"application/x-something" Content-Type is more likely to be handled
reasonably (by default, with a download offer) by more clients.
> Unfortunately, getting gzip and bzip2 recognized as an official (non-"x")
> type or encoding isn't likely.
It won't happen if nobody tries to register it with IANA.
Klaus
