• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1145
  • Last Modified:

Web.config allowoverride

I had a CMS which is having a web.config file.

I had a webservice which I had hosted as IIS Application inside the same site which is having its own web.config.

The webservice is referring the <httpModules> and <httpHandlers> from the root web.config and throws "unable to load type" error. S, I had places those <httpModules> and <httpHandlers> inside a location tag in root's web.config file with allowOverride="false"

Now my web service works fine, but some of the functionalities in the CMS didn't work because of this. If I move the <httpModules> and <httpHandlers> outside the location tag it works fine.

Now My question is why the allowoverride affects my root application. I believe this setting was for the child applications inside the same website.
  • 2
1 Solution
Alfred A.Commented:
You might try locking down your default loaded httpModules and httpHandlers set to avoid being changed with the introduction of allowOverride="false".  This will prevent applications removing or clearing default handlers and modules.


      <httpModules lockElements="clear,remove">

      <!-- Long list of httpModules -->


      <httpHandlers lockElements="clear,remove">

      <!-- Long list of httpHandlers -->


radcaesarAuthor Commented:
You are not getting my problem correctly I think.

Anyway, I had solved it, The solution is using inheritInChildApplications="false" instead of allowOverride="false" which solves the problem.

Else, I need to use "Remove" Verb manually in child web.config.
radcaesarAuthor Commented:
Managed to solve my problem

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now