Macromedia colfusion mx 7 Manual
Setting MIME types
139
You can also use multiple instances of the MIME type criteria, each with a single parameter value,
where quotation marks are necessary only if you use the wildcard character (*). For example:
where quotation marks are necessary only if you use the wildcard character (*). For example:
-mimeinclude text/plain
-mimeinclude ’application/*’.Setting MIME Types
-mimeinclude ’application/*’.Setting MIME Types
MIME types and web crawling
When you index a website, Verity Spider evaluates your MIME type criteria against the "Content-
Type" HTTP headers sent by the web server hosting that website. That web server passes along
MIME type information based on its own internal tables.
Type" HTTP headers sent by the web server hosting that website. That web server passes along
MIME type information based on its own internal tables.
When you encounter MIME types being dropped, make sure that the web server you are indexing
has the necessary MIME type information. For information about specifying MIME types, see
the documentation for your web server.
has the necessary MIME type information. For information about specifying MIME types, see
the documentation for your web server.
You can examine the indexing job’s log files for indications that files are being skipped due to
MIME types. For example, a typical ASCII file you might want indexed is a log file
(filename.log). Unless the web server understands that files with .LOG extensions are ASCII text,
of MIME type text/plain, you will see in the indexing job log file that .LOG files are skipped
because of MIME type, even if you use the following:
MIME types. For example, a typical ASCII file you might want indexed is a log file
(filename.log). Unless the web server understands that files with .LOG extensions are ASCII text,
of MIME type text/plain, you will see in the indexing job log file that .LOG files are skipped
because of MIME type, even if you use the following:
-mimeinclude ’text/*’
MIME types and file system indexing
When you index a file system, Verity Spider reads filenames and evaluates your MIME type
criteria against an internal, compiled list of known MIME types and associated file extensions.
You cannot edit this list. However, you can use the
criteria against an internal, compiled list of known MIME types and associated file extensions.
You cannot edit this list. However, you can use the
-mimemap
option to create a custom MIME
type mapping.
When you encounter MIME types being dropped, check whether Verity Spider recognizes that
particular MIME type. For more information, see the table,
particular MIME type. For more information, see the table,
.
You can examine the indexing job’s log files for indications that files are being skipped due to
MIME types. For example, a typical ASCII file you might want indexed is a log file
(filename.log). Since Verity Spider does not understand that files with .LOG extensions are ASCII
text, of MIME type text/plain, you will see in the indexing job log file that .LOG files are skipped
because of MIME type, even if you use the following:
MIME types. For example, a typical ASCII file you might want indexed is a log file
(filename.log). Since Verity Spider does not understand that files with .LOG extensions are ASCII
text, of MIME type text/plain, you will see in the indexing job log file that .LOG files are skipped
because of MIME type, even if you use the following:
-mimeinclude ’text/*’.Setting MIME Types
Indexing unknown MIME types
Whenever you find MIME types being dropped, or you know you will be indexing files whose
extensions are not known to Verity Spider by default, use the
extensions are not known to Verity Spider by default, use the
-mimemap
option to point to a file
that contains your own custom mappings for file extensions and MIME types.
You can also use the regular expression ’*/*’ for your MIME type criteria; for example:
-mimeinclude ’*/*’