- Overview
- Installation & Uninstallation
- Local and remote management using IIS 7
- Context and processing order
- Apache compatibility
- Modules
- core functions
- mod_antibot
- mod_asis
- mod_auth_basic
- mod_auth_digest
- mod_authn_anon
- mod_authn_dbd
- mod_authn_default
- mod_authn_file
- mod_authz_default
- mod_authz_groupfile
- mod_authz_host
- mod_authz_user
- mod_cache
- mod_dbd
- mod_deflate
- mod_developer
- mod_dir
- mod_disk_cache
- mod_env
- mod_evasive
- mod_expires
- mod_filter
- mod_gzip
- mod_headers
- mod_hotlink
- mod_linkfreeze
- mod_log_config
- mod_logio
- mod_mem_cache
- mod_mime
- mod_proxy
- mod_replace
- mod_rewrite
- mod_seo
- mod_setenvif
- mod_so
- mod_speling
- mod_usertrack
- mod_xsendfile
- Articles
- Release history
- Troubleshooting
- License agreement
NTFS permissions requirements
Automatic installation of Helicon Ape on a clean default Windows system does not require any permissions tweaking. But installation of some other products like Plesk, IIS Lock Down Tool, etc. may tighten server security and prevent Helicon Ape from correct operation.
To ensure flawless Helicon Ape operation, the IIS Application Pool user must have Read and List folder content permissions to Helicon Ape installation folder and every folder with .htaccess files. By default IIS Application Pool users are members of <MACHINE>\IIS_IUSRS usergroup, so you can provide required permissions to this group if your server is configured according to Microsoft recommended guidelines.
Helicon Ape is a .NET module that runs in context of IIS Application Pool, so various .NET trust levels and custom .NET restrictions can also affect it's operation. If all NTFS permissions are granted but configuration files are not working, please refer to troubleshooting section of this documentation.