I have an HttpModule that I want to register in a child web.config (ie. not in the application level web.config). Now, the HttpModule works fine when it's in the application's root web.config.. but. if I put it in the web.config of one of the subdirectories.. it doesn't fire at all (ie the Init Method never fires).

I looked in the MSDN documentation and it says thatte httpModules element can be configured at any web.config level.  If this is the case, what gives?

ps. I haven't posted the code for the module because I've proven functionality, just not when I move it to the desired config level.

Any thoughts?

--D

Im not sure you can add it at different levels!?  I would imagine you would add it at the root level and then look at the request to see if it should be run or not.. i.e check the RawUrl for the correct level?  What are you trying to do?

Hi there

I agree with David.
The Modules would only be activated if you are in that level where the config is applied, not above and below.

if registered in a child config file, I think(not sure) the module will fire when the page in the child folder is requested, it will not fire when other pages are requested.