Problem mapping HttpHandler --> HTTP Error 404 Not Found

Question

I am having problems trying to map an HttpHandler in the web.config.

This is the relevant config bit:

<httpHandlers>
  <add verb="*" path="*.hndlr" type="MyAssembly.MyHandler, MyAssembly" validate="false" />
</httpHandlers>

When I navigate to http://localhost/myApp/whatever.hndlr I am getting a server error 404 (not found).

It's the 1st time I am hooking up an HttpHandler so I might be missing something - any help appreciated!

UPDATE:

I managed to get it working using both answers so far - who's able to explain why it works gets the answer marked!

This is my config (won't work if you don't have both - I am running IIS7 in classic mode)

System.web:

<httpHandlers>
    <add verb="*" path="*MyHandler.hndlr" type="MyAssembly.MyAssemblyHandler, MyAssembly" validate="false"/>
</httpHandlers>

System.webserver:

<handlers>
    <add name="MyHandler" verb="*" path="*MyHandler.hndlr" type="MyAssembly.MyAssemblyHandler, MyAssembly" validate="false" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script"/>
</handlers>

Further to your update, if you are using IIS6 antything you put in the System.webserver section will be ignored as this is used only in IIS7 Integrated Pipeline mode. THe only reason to have both would be to have a single web.config that is valid for IIS7 pipelined and calssic mode and IIS6. — Ben Robinson, May 20 '10 at 16:22
sorry it's IIS7 - but does that change things? If I remove the bit in the system.webserver section it doesn't work (404 not found) and we are in classic mode for compatibility reasons. — JohnIdol, May 20 '10 at 17:07
and if I comment out the one in system.web I get "Failed to Execute URL" - it works only with both for some funny reason! :) — JohnIdol, May 20 '10 at 17:18

score 30 · Accepted Answer · answered May 18 '10 at 15:45

30

Are you using IIS7, if so is the application pool running in classic or pipelined mode? If it is IIS7 in pipelined mode then the handler reference needs to go into the following section

<system.webServer>
    <handlers>
    </handlers>
<system.webServer>

rather than in the following section.

<system.web>
    <httpHandlers>
    </httpHandlers>
</system.web>

answered May 18 '10 at 15:45

Ben Robinson

21,601
5
62
79

tried (had to add name="MyHandler" to the attributes) - looks promising but getting a different error now --> HTTP Error 500.21 - Internal Server Error Handler "MyHandler" has a bad module "ManagedPipelineHandler" in its module list – JohnIdol May 18 '10 at 15:56
to answer your other question I am running in classic mode (not pipelined) - which explains why I am getting the error described in the comment above :) – JohnIdol May 18 '10 at 16:05
Yes the solution was a bit of a mixture between the two answers - I am about to post the solution and who's able to better explain what the heck is going on gets the points! :) – JohnIdol May 20 '10 at 15:22

CResults · Answer 2 · 2011-03-09T14:53:32.407

11

Just as a guide for those stuck with this problem I found the crucial attribute to be..

resourceType="Unspecified"

I originally followed a Microsoft example to set this up and they had it as

resourceType="File"

which just kept giving me 404 errors. My HTTPHandler is returning graphics.

Hope this helps :)

edited Mar 09 '11 at 14:53

answered Mar 09 '11 at 14:38

CResults

5,100
1
22
28

score 5 · Answer 3 · edited Oct 14 '15 at 10:49

5

i am using IIS7, the solution is:

in section

<system.web>
    <httpHandlers>
        <add verb="*" path="*.ashx" type="CVOS.MyDocumentHandler"/>
    </httpHandlers>
<system.web>

and section

<system.webServer>
    <handlers>
       <add name="pdfHandler" verb="*" path="*.ashx"   type="CVOS.MyDocumentHandler" /> 
    </handlers>
</system.webServer>

edited Oct 14 '15 at 10:49

evilone

22,410
7
80
107

answered Jan 23 '13 at 14:47

CARLOS HERNANDEZ

51
1
1

score 4 · Answer 4 · answered May 18 '10 at 16:49

What is the extension of your handler? If you are using a custom extension like .hndlr you may also need to add a ScriptMap in IIS and point it to the ASP.NET runtime so that IIS can forward the request to the correct processor.

In IIS7 go to your website
Under the IIS group go to Handler Mappings
Under Actions click Add Script Map
Set Request Path to *.hndlr
Set Path to the ASP.NET runtime (%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll) or whatever version you are running.

Then in your web.config you will need to register the handler in the appropriate section as described in the other answer.

score 2 · Answer 5 · answered Jul 30 '14 at 05:34

It is also possible to experience this error if you have set up the handler for 32 bit, but you are running in 64 bit (or vice versa). It's easy to set up both and have all the bases covered.

Note "preCondition", and "scriptProcessor" differences.

<handlers>
    <add name="MyHandler_32bit" verb="*" path="*MyHandler.hndlr" preCondition="bitness32" type="MyAssembly.MyAssemblyHandler, MyAssembly" validate="false" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" />
    <add name="MyHandler_64bit" verb="*" path="*MyHandler.hndlr" preCondition="bitness64" type="MyAssembly.MyAssemblyHandler, MyAssembly" validate="false" modules="IsapiModule" scriptProcessor="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" />
</handlers>

score 2 · Answer 6 · answered Aug 08 '17 at 08:04

None of the previous answers worked for me.
I'm using IIS 8.5, .Net v4.0, Integrated, and was still getting a 404 with the following handler config:

<system.webServer>
    <handlers>
       <add name="testEmail" path="*.em" verb="*" type="MyApp.testRazorEmailHandler, MyApp" resourceType="Unspecified" requireAccess="Script" />
    </handlers>
</system.webServer>

I enabled tracing and found the following :

116. -HANDLER_CHANGED 

    OldHandlerName              testEmail 
    NewHandlerName              System.Web.Mvc.MvcHandler 
    NewHandlerModules           ManagedPipelineHandler 
    NewHandlerScriptProcessor
    NewHandlerType              System.Web.Mvc.MvcHandler, System.Web.Mvc, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

As you can see it looks like it had correctly picked up the request using my custom HttpHandler testEmail but MVC had stolen it.
I opened my route definitions in RouteConfig.cs and found that adding:

   routes.IgnoreRoute("{resource}.em");

I got it to ignore requests meant for my Handler.
Hope this helps someone - I was tearing my hair out!

This has saved my bacon. Thanks ever so much. – David Christopher Reynolds Sep 18 '18 at 14:40 — David Christopher Reynolds, Sep 18 '18 at 14:40

score 1 · Answer 7 · answered Jan 22 '14 at 18:50

Hopefully my solution will help others. On a server move from IIS6 to 7.5, both .Net 4.0 Integrated, I had a Captcha control that quit working. It turns out that removing this attribute preCondition="integratedMode,runtimeVersionv2.0" from the <add> node in <system.webserver><handlers> resolved the issue.

Harv · Answer 8 · 2023-02-17T16:00:15.467

This seems to be an edge case, but I had a customer where our httpHandler used in our application did not work on any of their servers. The handler pointed to an .ashx page and it was called from JavaScript.

The handler mapping showed up in IIS, the handler factory was there, but I would get a 404 when the browser requested the ashx page associated with the handler. After many different attempts to fix we finally browsed to the file in IIS on the server and it specifically showed a 404.7 being returned with this message.

•Request filtering is configured for the Web server and the file extension for this request is explicitly denied.

•Verify the configuration/system.webServer/security/requestFiltering/fileExtensions settings in applicationhost.config and web.config.

If you get this then Request Filtering is enabled for the .ashx extension at either your app or site level. Go to the Request Filtering option in IIS at both your site and app level and verify that the extension is not blocked. There are two different ways Request Filtering can be configured.

The default seems to be that it explicitly blocks only file extensions that are configured in the list (blacklist). The other way it can be configured is that only files specifically configured as allowed in the list are let through (whitelist). This second option is how the customer had configured all of their Windows Servers by default and it turns out that the .ashx file extension was not in the list of allowed extensions.

score 0 · Answer 9 · answered Jan 06 '22 at 00:37

0

This is the first thread that appears when I look for a verb that responds with a 404. In my case the solution was a configuration of VS

Tools > Options > Web projects > [x] Use 64 bit version

Sorry, my VS is in spanish

answered Jan 06 '22 at 00:37

hestellezg

3,309
3
33
37

Problem mapping HttpHandler --> HTTP Error 404 Not Found

9 Answers9

Linked