Question

I have an application that depends on a generic HttpHandler I created, and it works fine. The problem is that that there are many other applications under the same folder in IIS, and these other apps don’t need to use and don’t know (mustn’t know) about this handler.
However, the Web.Config in which I register it ends up applying to all folders on the same level and all subfolders, and this is what I want to avoid.

Changing the structure of the apps inside IIS is not a possibility, unfortunately.

I thought of using the < location > tag on Web.config, but I’m under the impression it only changes rights to access and not visibility.

Any suggestions on how this can be overcome?

Answer 1

HttpHandlers are configured at the application level. Are these subfolders you speak of really separate applications? If not, there’s not much you can do about it… Aristos’ suggestion might be viable though. If they are really applications, you’ll just have to specifically remove the handler from those applications.

http://msdn.microsoft.com/en-us/library/e0dzxdza%28VS.71%29.aspx