G
Guest
I have an http handler that I’d like to be recognized for every site on a server. The http handler is similar to what the trace.axd handler, in that there is no actual file that exists on the hard drive to process. When the hander gets called, it generates the html and dumps the html to the context.Response object, which then gets rendered to the client.
I have the handler in the GAC, all my web sites have the appropriate web.config section. And I’ve added the file extension ‘.mgr’ to IIS. Here is the problem. If I register the file extension to a specific web site under the Default Web Site in IIS, then everything works fine. But if I register the file extension just for the Default Web Site on IIS (the one that all the other web sites that run on port 80 reside under), then it doesn’t work. If I have 25 sites running under the Default Web Site, do I have to register my handler individually for each site? Or shouldn’t the settings for the Default Web site trickle down to the sub sites
I'm using IIS 5.0 on an XP machine
I have the handler in the GAC, all my web sites have the appropriate web.config section. And I’ve added the file extension ‘.mgr’ to IIS. Here is the problem. If I register the file extension to a specific web site under the Default Web Site in IIS, then everything works fine. But if I register the file extension just for the Default Web Site on IIS (the one that all the other web sites that run on port 80 reside under), then it doesn’t work. If I have 25 sites running under the Default Web Site, do I have to register my handler individually for each site? Or shouldn’t the settings for the Default Web site trickle down to the sub sites
I'm using IIS 5.0 on an XP machine