Home/ Questions/Q 3964762
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T03:22:25+00:00

I need a simple HttpHandler to handle specific non-existant paths in my ASP.NET project.

  • 0

I need a simple HttpHandler to handle specific non-existant paths in my ASP.NET project. I’m using sitefinity 4. I wrote the handler but whenever I try to run the site, I get a frustrating error

The WebResource.axd handler must be registered in the configuration to process this request.

I was putting the handler in the system.web part of the config but it looks liek VS2010 still uses IIS 6 for it’s built in web server so I went ahead and switched it to use IIS 7 (local) and moved the registration of the handler to system.webServer and it works when I hit a non existant url but if I try to go to the site normally (valid url) I get that dang error again.

It worked once, giving me the correct site on a valid url but now it just continues to give me trouble.

How can I resolve this issue? I don’t want to add that entry to the config as it wasn’t there when I created the project and it only started when I added my handler.

EDIT: Only happens when I use Path=”*” so how do I do a wildcard? I don’t want to map a handler to catch a 404 page.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Froget it. No one seems to know even though I know i’m not the only one who has needed to do this. I got 404 to work but ONLY when I request a file, not a folder so thats a bust.

    I found that Global.asax will hit under integrated mode so I just moved my code to the Application_BeginRequest() and it’s working just fine. If anyone else has a better answer I will give them credit.

    • 0