IIS 6.0 cannot process unknown MIME types

When you request a file from the IIS 6.0 Web server, and the file extension is not the MIME type defined on the Web server, you will see the following error message:

HTTP Error 404-the file or directory cannot be found.

Cause

Earlier versions of IIS contain wildcard mime ing, allowing IIS to process any file without considering the extension. IIS 6.0 does not contain this wildcard mime ing and cannot process the number of characters in IIS...

Earlier versions of IIS contain wildcard mime ing, allowing IIS to process any file without considering the extension. IIS 6.0 does not contain this wildcard mime ing and cannot process any type of extension defined beyond the mimemap node in the IIS metadatabase.

Warning: Improper editing of metadatabase may cause serious problems. You may need to reinstall all products that use metadatabase. Microsoft cannot guarantee that the problem is caused by incorrect metadata editing...

Warning : If you do not edit the metadatabase correctly, it may cause serious problems. You may need to reinstall all the products that use the metadatabase. Microsoft cannot guarantee that you can solve the problem caused by incorrect metadata editing. You are at your own risk to edit the metadatabase.

Note:: Back up the metabase every time you edit it.

To define the MIME type for a specific extension, follow these steps:

1. Open the IIS Microsoft Console (MMC), right-click the name of the local computer, and click Properties ".
2. Click "MIME type ".
3. Click new ".
4. In the "extension" box, type the desired file extension (for example,. PDB).
5. In the "MIME type" box, typeApplication/octet-stream.
6. Apply new settings. Note that you must restart the Web Publishing Service or wait for the workflow to take effect. In this example, IIS can now process files with the. PDB extension.

If you want to process all files without considering the file extension (for example, if you cannot predict all files to be processed), follow these steps to add wildcard ing:

Note:: You can only add wildcard ing to IIS mime ing during troubleshooting as a temporary solution. After you confirm that the MIME type is missing, delete the wildcard ing and add a specific mime ing of the MIME type to be processed.

1. Open the IIS Microsoft Console (MMC), right-click the name of the local computer, and click Properties ".
2. Click "MIME type ".
3. Click new ".
4. In the extension box, type an asterisk (*).
5. In the "MIME type" box, typeApplication/octet-stream.
6. Apply new settings. Note that you must restart the Web Publishing Service or wait for the workflow to take effect.

Note:: In addition to the above changes on the global layer of IIS, you can also add the required MIME types at the lower layer of the metabase. In this case, you can specify a site or directory with a specific file extension, rather than allowing all sites to process the extension globally.

This phenomenon is caused by design.

This phenomenon is caused by design.

The product documentation provides more information about the use of the MIME type. To view this document, visit the following Microsoft Website: http://www.microsoft.com/t...

The product documentation provides more information about the use of the MIME type. To view this document, visit the following Microsoft Website:

Http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/standard/wsa_mimemapcfg.asp? Frame = true (Http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/standard/wsa_mimemapcfg.asp? Frame = true)

You can also access the product documentation through IIS manager.