Description
AddType associates file names and/or extensions
with mime types, for protocols that
don't automatically include mime types,
such as file:/// and ftp://.
Note:
The protocols http:// and https://
automatically include mime types in the response headers, so there is
usually no need to use AddType if you index only
HTTP and HTTPS servers.
However, in case when a HTTP or a HTTPS
server returns wrong mime type for some reasons, you can use
UseRemoteContentType no
to have mnoGoSearch ignore the response
headers and to use the mime types defines by AddType
commands instead.
The first two optional parameters specify comparison type.
The default comparison type is String and
Case (case insensitive string pattern match with
? and *
wildcards meaning one character
and
any number of characters
correspondingly).
If the mime type parameter contains
spaces (for example, when character set specification is added),
it should be put into single or double quotes.
Note:
Russian webmasters often use *.htm extension
for
windows-1251 documents and
*.html for UNIX
koi8-r documents.
The pattern parameter can be repeated multiple
times, to associate a mime type with multiple extensions in a single
command.