|Posted: 07 December 2010 at 8:22am
Thanks for the files.
We have to test, I’m not sure why it’s happening. The web.config is full of
many settings, there are several other modules. Helicon Ape is set for the
whole server. I mean it’s installed globally. Even though you have no
.htaccess—IIS still runs Ape on every request.
As we test, you can simply disable Helicon Ape for that website. Run Helicon
Ape manager, select the website in the tree and in the context menu choose
“Disable Helicon Ape”.
I will have a problem if this is not resolved. Now we have to disable ape manually for each site this reseller will create. Also when this customer want to use password protected files/directories we need to enable ape for this. Can you point us in the right direction maybe? We have enable all modules from ape but may not need them all. Could this be related to a ape module witch we can disable?