Last post Oct 07, 2008 11:02 AM by DarrenAllen
Sep 30, 2008 12:06 PM|DarrenAllen|LINK
I have a httpHandler implemented in vs2005, IIS5, .Net 2.0. If I use the "Visual Studio Development Server", it works just fine. However, if I configure a website http://localhost/mysite.... the httpHandler does not function.
Can anyone point me to the proper solution?
HttpHandler "ASP Development Server"
Sep 30, 2008 02:00 PMfirstname.lastname@example.org|LINK
Just curious as to any error messages that are being promoted? Also how are you calling your handler on your localhost server?
On the development server your path would be
However from what it looks like on your local host server (no development) you should be using
http://localhost/mysitename/httphandler (as you have another directory after your root directory which contains your site)
Sep 30, 2008 05:06 PM|DarrenAllen|LINK
I get what you are saying about the "another" directory and that is not the issue. I have tried several things in that area to ensure that is not the problem. I should add in that I also have this same basic issue on a production level IIS box running IIS
6.0. I have the same exact code deployed to the same IIS box under 2 different root nodes. One works and the other does not. From what we can see/find, other than the names being different, those web sites are identical.
Sep 30, 2008 06:36 PMemail@example.com|LINK
Exactly how are your sites setup and how are you calling the handler?
Oct 07, 2008 11:02 AM|DarrenAllen|LINK
Thanks for your help.
I eventually found the issue. The web server admin had told me the web servers were setup "identical" and I made the mistake of listening to him.
The wildcard mapping on the production server(s) did not exist, so when I requested a non ISAPI_DLL mapped file like (PDF), it didn't fire the handler.