Jonathan de Boyne Pollard
2004-12-10 04:42:18 UTC
MS> at what point are the mimetypes for any url generated?
If the URL employs the "file:" or "ftp:" schemes, most web browsers
deduce the content type from the filename, employing a "mime.types"
database of one sort or another.
If the URL employs the "http:" or "https:" schemes, the content type is
passed, in metadata attched to the actual object data, from the content
HTTP server. Most content HTTP servers themselves employ a "mime.types"
database of some sort to deduce the content type from the filename.
For examples: With vanilla "publicfile", the filename to content type
mappings follow a fixed set of rules.
(<URL:http://cr.yp.to/publicfile/filetypes.html>) With "publicfile" plus
Uwe Ohse's modifications, the filename to content type mappings are
stored in the environment variables of the server instance process.
With Apache, the filename to content type mappings can be stored in a
"mime.types" file, in the "httpd.conf" file, or in a ".htaccess" file.
Note that plug-ins, in both web browsers and content HTTP servers, can
modify the determinations of content types.
If the URL employs the "file:" or "ftp:" schemes, most web browsers
deduce the content type from the filename, employing a "mime.types"
database of one sort or another.
If the URL employs the "http:" or "https:" schemes, the content type is
passed, in metadata attched to the actual object data, from the content
HTTP server. Most content HTTP servers themselves employ a "mime.types"
database of some sort to deduce the content type from the filename.
For examples: With vanilla "publicfile", the filename to content type
mappings follow a fixed set of rules.
(<URL:http://cr.yp.to/publicfile/filetypes.html>) With "publicfile" plus
Uwe Ohse's modifications, the filename to content type mappings are
stored in the environment variables of the server instance process.
With Apache, the filename to content type mappings can be stored in a
"mime.types" file, in the "httpd.conf" file, or in a ".htaccess" file.
Note that plug-ins, in both web browsers and content HTTP servers, can
modify the determinations of content types.