This is a new thing that I learned today. To give you a background, we have a running suite of applications on Windows2000 and IIS 5.0. Now, there is a move to upgrade the apps to Win03. After installing IIS, we realized the ASP files are not at all running on the web server while the HTML files are fine. Using the good old experience we thought it must be an installation problem, and the IIS got a faulty setup.
Then we realized the new administrative control came with IIS 6.0. It allows you to enable/disable dynamic content. Referring back to my original problem, the extension ASP was set disabled through this control, perhaps it was a default setting, or may be something really goofed up during the installation steps. But for sure, this was not a old-day's installation glitch, which could be resolved only by uninstallation and reinstallation.
IIS Manager for IIS 6.0 provides interfaces for allowing or prohibiting certain extensions related to dynamic content. You are allowed to allow/prohibit all ISAPI and CGI extensions on a server, but it's not a recommended practice to allow all ISAPI/CGI extensions to prevent the machine being suceptible to computer viruses or worms that use these technologies. So, as a good practice, allow only the required extensions.
You will find more information in the following URL http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/a9fc0395-f03b-4213-9c62-1592bcfcf53f.mspx
No comments:
Post a Comment