Article ID: 324068 - View products that this article applies to.
This article was previously published under Q324068
This article describes how to migrate UNIX permissions to the IIS permission system and how to set IIS permissions for a Web site, a folder, or file.
The Read permission in IIS is similar to the Read permission bit for files in Apache/UNIX. The Write permission in IIS is used only when you are using Active Server Page (ASP) scripts or Web Distributed Authoring and Versioning (WebDAV) to provide update functionality for a file; therefore, this permission is similar to the Write permission in Apache/UNIX for WebDAV only. The Execute permission in UNIX that is combined with the AddHandler directive indicates to Apache that a particular file is a script that should be run and not returned as a raw file. In IIS, Execute permissions are granted on a Web site basis or a folder basis only; you cannot enable or disable individual files as scripts in this way. However, the extension/handler combination does apply. You grant Execute permissions for a folder, and then associate an extension with a specific scripting engine.
This behavior has limitations. For example, you cannot use a blanket .cgi file name extension and rely on the UNIX header line to select the corresponding scripting language. This limitation may cause problems during migration. In this situation, you can associate the .pl file name extension for Perl scripts the .py file name extension for Python scripts.
For additional information about securing IIS for a migration from UNIX to Windows, click the article number below to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/324216/EN-US/ )HOW TO: Secure IIS in a UNIX-to-Windows Migration
Article ID: 324068 - Last Review: November 21, 2006 - Revision: 3.3