![[APACHE DOCUMENTATION]](../images/sub.gif)
mod_mime.c file, and is
compiled in by default. It provides for determining the types of files
from the filename.
The filename of a document is treated as being composed of a basename followed by some extensions, in the following order:
base.type.language.encThe type extension sets the type of the document; types are defined in the TypesConfig file and by the AddType directive. The language extension sets the language of the document, as defined by the AddLanguage directive. Finally, the enc directive sets the encoding of the document, as defined by the AddEncoding directive.
The AddEncoding directive adds to the list of filename extensions which filenames may end in for the specified encoding type. Mime-enc is the mime encoding to use for documents ending in extension. Example:
AddEncoding x-gzip gz
AddEncoding x-compress Z
AddHandler maps the filename extension extension to the
handler
handler-name. For example, to activate CGI scripts
with the file extension ".cgi", you might use:
AddHandler cgi-script cgi
Once that has been put into your srm.conf or httpd.conf file, any
file ending with ".cgi" will be treated as a CGI
program.
The AddLanguage directive adds to the list of filename extensions which filenames may end in for the specified content language. Mime-lang is the mime language of files with names ending extension, after any content encoding extensions have been removed. Example:
AddEncoding x-compress Z
AddLanguage en .en
AddLanguage fr .fr
xxxx.en.Z will be treated as being a compressed
English document. Although the content language is reported to the client,
the browser is unlikely to use this information. The AddLanguage directive
is more useful for content negotiation, where the server returns one
from several documents based on the client's language preference.The AddType directive adds to the list of filename extensions which filenames may end in for the specified content type. Mime-enc is the mime type to use for documents ending in extension. after content-encoding and language extensions have been removed. Example:
AddType image/gif GIF
Note that, unlike the NCSA httpd, this directive cannot be used to set the type of particular files.
When placed into an .htaccess file or a
<Directory> or <Location section,
this directive forces all matching files to be served
as the content type given by media type. For example, if you
had a directory full of GIF files, but did not want to label them all with
".gif", you might want to use:
ForceType image/gif
Note that this will override any filename extensions that might media type.
When placed into an .htaccess file or a
<Directory> or <Location section,
this directive forces all matching files to be parsed through the
handler
given by handler-name. For example, if you had a
directory you wanted to be parsed entirely as imagemap rule files,
regardless of extension, you might put the following into an
.htaccess file in that directory:
SetHandler imap-file
Another example: if you wanted to have the server display a status
report whenever a URL of http://servername/status was
called, you might put the following into access.conf:
<Location /status>
SetHandler server-status
</Location>
TypesConfig conf/mime.typesThe TypesConfig directive sets the location of the mime types configuration file. Filename is relative to the ServerRoot. This file sets the default list of mappings from filename extensions to content types; changing this file is not recommended. Use the AddType directive instead. The file contains lines in the format of the arguments to an AddType command:
mime-type extension extension ...The extensions are lower-cased. Blank lines, and lines beginning with a hash character (`#') are ignored.
