HTTP Module Not Invoking

Discussion in 'ASP.NET / ASP.NET Core' started by hockeyporta, Mar 1, 2010.

  1. I have an HTTP Module in place in my web application that works fine while running on my local machine. However, after deploying the application to the DASP server, the http module is not invoked. Is there something that I'm missing? Is there a security setting that I must include in the web.config? Any help would be greatly appreciated.
     
  2. Working fine locally on which IIS version?
    Deployed to DASP on which IIS version?
     
  3. The HTTP Module works fine while running the web application in Visual Studio 2008 with the ASP.Net Development Server.

    The web app is deployed to DASP on IIS7.
     
  4. The integrated VS web server (cassini) uses the old IIS6 web.config syntax so if you've not already done so, you need to duplicate your httpmodule configuration into the <system.webserver> section to enable it to work on IIS7.

    It's no problem leaving the configuration in the <system.web><httpModules> section for backward compatibility support however.
     
  5. Thanks for your prompt responses.

    Updating my HTTP Configuration in the web.config fixed the issue that I was having. The following is required in the web.config to have an HTTP Module invoked while running your website on IIS7:

    HTML:
    <system.webServer>
        <modules>
              <add name="MyHTTPModule" type="HockeyPortals.HttpModules.MyHTTPModule"/>
        </modules>
    </system.webServer>
    
     
  6. That's the one, thanks for confirming the fix.
     

Share This Page