I\'m having troubles with a custom Error handler I built. It should be a HttpModule
, but when I add it to my web.config
\'s system.webServer/modul
I had this problem and discovered that not turning off customErrors prevented the handler from triggering.
ie: this is required in your config for the Error event to be captured in the HttpModule:
<system.web>
<customErrors mode="Off" />
</system.web>
From what I can see you're on the right track. Have you made sure your site's application pool is set to Managed Pipeline mode?
Also if you're testing this with the built in Visual Studio web server (Cassini) then the <system.webServer>
section will be ignored. You'll need IIS7 or IIS7.5 Express if you want the module to load from there.
I was experiencing the same problem of a handler that is not getting triggered, by doing following change to the above code helped me to resolve this issue. Instead of creating a new event handler I just attached the method with same signature to that event.
application.Error += ErrorHandler;
This works for me, still analyzing what is the reason behind this way attaching a handler works in IIS7.