Home/ Questions/Q 332179
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T09:50:36+00:00

I wrote a tiny HttpHandler, which works beautifully on my machine. However, once it

  • 0

I wrote a tiny HttpHandler, which works beautifully on my machine. However, once it was deployed to our staging server, requesting it gave an 404. I usually prefer configuring HttpHandlers in web.config, but this apparently didn’t work on the server: I fixed it by creating an .ashx file containing just the reference to my HttpHandler.

The .ashx file:

<% @ WebHandler class="MyNamespace.MyProject.MyHttpHandler" %>

The web.config setting:

<httpHandlers>
  <add verb="GET" path="myhandler.ashx" type="MyNamespace.MyProject.MyHttpHandler"/>
</httpHandlers>

I assume the problem is caused by the server using a “special” port (888, don’t ask why) for the website. Can it be something else, what could I be missing?

Why am I seeing this behavior on the server? The HttpHandler runs fine on my local machine with configuration just in web.config, and here it’s also served from a “random” port, i.e. http://localhost:61229/myhandler.ashx.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It sure sounds like the web.config setting is not being found.

    Is this IIS 7 by any chance? In that case make sure you’re putting the handler in the <system.webServer> and its <handlers> section.

    • 0