Clever Geek Handbook

Http module and Http handler do not start when under the virtual directory of ASP.NET website

Problem: There is a website (localhost: 85) that is configured to C: \ abc. I have created a separate website that has HttpModule and HttpHandler. This new website does not have to be in the main application (C: \ abc). So I put a separate folder like D: \ xyz. And configured the virtual directory under port 85.

Using an ISAPI filter whenever associated with an xyz application request, I map the url to \xyz\URIRequest.aspx?RequestURL=ActualQuerystring

.

The problem is the request reaches the XYZ Global.asax Application_start (). But it doesn't go through the pipeline (httpmodule and httphandler works).

If I set up this XYZ app as a standalone website or create a virtual directory on a website without web.config. The app works fine.

Solution tried:

  • Moved the xyz application web.config entry to abc web.config application and copied the xyz application dll attachments to the ABC / bin directory.
+2


source to share


2 answers


Have you marked the virtual directory as an application? those. does it have a gear in IIS? This is a common problem where the subfolder does not execute as intended.



+1


source


The way virtual directories work in IIS, when it comes to web.configs, they are "inherited" from the application above the virtual directory, all the way down to machine.config in "windows \ Microsoft.NET \ etc ...".



0


source






More articles:


All Articles