[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev mime-types, server responsibility, etc..
From: |
David Woolley |
Subject: |
Re: lynx-dev mime-types, server responsibility, etc.. |
Date: |
Sun, 3 Jan 1999 12:09:03 +0000 (GMT) |
>
> > Isn't there a 8 bit qualifier that one can specify along with text/plai=
> n?
HTTP is 8 bit by default. It is possible to add character set qualifiers.
>
> HTTP servers have a kind of mime.types files where any mime type can be
> attributed to any file extension.
That's an implementation detail, although it is true for most servers.
It is, however, possible to override on a file by file basis on good
servers, or vary the rules from directory to directory.
The problem that people may have is with cheap (or bundled) web space, in
that the administrators want to minimise the amount of work they do rather
than support people with uncommon file formats.
- lynx-dev mime-types, server responsibility, etc.., mattack, 1999/01/02
- Re: lynx-dev mime-types, server responsibility, etc.., Larry W. Virden, 1999/01/02
- Re: lynx-dev mime-types, server responsibility, etc.., Klaus Weide, 1999/01/02
- Re: lynx-dev mime-types, server responsibility, etc.., Ismael Cordeiro, 1999/01/02
- Re: lynx-dev mime-types, server responsibility, etc..,
David Woolley <=
- Re: lynx-dev mime-types, server responsibility, etc.., Ismael Cordeiro, 1999/01/05
- Re: lynx-dev mime-types, server responsibility, etc.., David Woolley, 1999/01/07
Re: lynx-dev mime-types, server responsibility, etc.., pg, 1999/01/02
Re: lynx-dev mime-types, server responsibility, etc.., Ismael Cordeiro, 1999/01/02