Article ID: 275601 - Last Review: March 17, 2008 - Revision: 5.0

Virtual directory names with executable extensions are not used correctly

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q275601
Expand all | Collapse all

SYMPTOMS

When a virtual directory name ends with an executable extension (such as .com, .exe, .dll, or .sh), the files in this virtual directory cannot be viewed with a Web browser.

If the execution rights are not set in this virtual directory, the following error message occurs:
403.1 - Forbidden: Execute Access Forbidden
If the execution rights are set (or write access), one of the following error messages occurs:
Error message 1
404 - File not found
Error message 2
401.3 - Unauthorized
Note Microsoft does not recommend having a virtual directory name that contains .asp because its content will be considered ASP content by Internet Information Services (IIS), regardless of the file types that are present in the virtual directory.

CAUSE

IIS interprets the virtual directory with an executable extension as an executable file and tries to run this file. The rest of the URL is passed in the Path_Info variable. Tools such as the FrontPage Server Extensions make use of this functionality.
APPLIES TO
  • Microsoft Internet Information Services 7.0
  • Microsoft Internet Information Services 6.0
  • Microsoft Internet Information Services 5.0
  • Microsoft Internet Information Server 3.0
  • Microsoft Internet Information Server 4.0
Back to the top
Keywords: 
kbpending kbprb KB275601