How Web Server Permissions Are Set
IIS Web server permissions can be configured to limit the access of anonymous users to your applications, and can also be configured to limit the viewing of source code over the Internet, even for users with Windows permissions (or access control entries).
It is important to understand the distinction between Web server permissions and NTFS permissions. Unlike NTFS, Web server permissions apply to all users accessing your Web sites. NTFS permissions apply only to a specific user or group of users with a valid Windows account. NTFS permissions control access to physical directories on your server, whereas Web permissions control access to virtual directories on your Web site.
When you package a site, the Web server permissions as set in the source site will be persisted. For example, if you set the Execute Permissions setting to Scripts and Executables in the root folder of the application on the source computer, the virtual root folder on the destination computer will have the same setting.
For example, the following table describes how the IIS permissions are set in the packages provided by Microsoft.
| Folder | Permissions |
|---|---|
| Root | Set Execute permission to Scripts and Executables. |
| Pipeline, Include, Template | Deny permission to read, write, and execute. |
.gif "Ee798076.note(en-US,CS.20).gif")
Note
- Site Packager does not preserve Windows access control lists (ACLs), which contain NTFS permissions. ACLs describe the groups and individuals who have access to specific objects in Microsoft Windows 2000. These objects include Active Directory directory service objects, local NTFS files and folders, the registry, and printers.
See Also
Where Resources and Data Are Unpacked
Running Site Packager from the Command Line
Copyright © 2005 Microsoft Corporation.
All rights reserved.