Article ID: 186803
This article was previously published under Q186803
This article has been archived. It is offered "as is" and will no longer be updated.
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
If you try to browse folders with extensions that are script-mapped, one of the following errors occurs:
In general, it is bad practice to name a folder using an extension that is MIME-mapped, but this holds especially true for scripted extensions. This is because it is common to pass information to a Web script that will be included as part of the PATH_INFO environment variable.
For example, a CGI program at the URL http://localhost/foo.cgi/default.htm
(http://localhost/foo.cgi/default.htm)receives "/foo.cgi/default.htm" in PATH_INFO.
To work around this problem, name Web folders without extensions, or use extensions that are not script-mapped.
On a system with a CGI-based Practical Extraction and Report Language (Perl) interpreter, save the following Perl script as "env.cgi" in your default "/scripts" folder.
When you browse to http://localhost/scripts/env.cgi/test.htm
(http://localhost/scripts/env.cgi/test.htm)you see the PATH_INFO environment variable reflect the information passed to the script as "/env.cgi/test.htm".