You can use the MIME type criteria options
-mimeinclude , -indmimeinclude, -mimeexclude and -indmimeexclude to include or exclude MIME types. Syntax Restrictions
When you specify MIME type criteria, keep in mind the following restrictions. Using the Wildcard Character (*)
The asterisk (*) wildcard character does not operate as a regular expression for the value of the MIME type criteria. Instead you can only use it to replace the entire MIME type or MIME sub-type.text/html:
text/html:
For example:
You can also use multiple instances of the MIME type criteria, each with a single parameter value, where quotes are necessary only if you use the wildcard character (*).
For example:
- -mimeinclude text/plain
- -mimeinclude application/*
When you encounter MIME types being dropped, make sure the web server you are indexing has the necessary MIME type information. See the documentation for your web server for information about specifying MIME types.
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:
When you encounter MIME types being dropped, check if the Verity Spider recognizes that particular MIME type. See the table, "Known MIME Types for File System Indexing," later in this chapter.
For example:
Furthermore, you should also use inclusion and exclusion criteria to finely control what is indexed.
-exclude, -indexclude, -mimeexclude, or -indmimeexclude) to exclude extensions you know you do not want to index. For example:
-include, -indinclude, -mimeinclude, or -indmimeinclude) to specify them. For example: