Sometimes you have a problem for which the solution is so simple and obvious, you can't believe you've overlooked it.
It happened to me a short while ago with an HttpHandler in a website that is using a presentation-service for the presentation-logic (I'll post about this service later). All the pages in the website are dynamically build, based on the results of a call to the presentation-service. The url's don't refer to existing pages and the HttpHandler is supposed to handle all incoming requests. Except, all I got was 404's. I had configured the necessary wildcard mapping, but it took me a while to find that the "Verify that file exists" option was checked. With this option checked, the HttpHandler is only called when the request matches to a physical file on disk. Which of course defeats the purpose of my HttpHandler.
Here's how to correctly configure a wildcard mapping in IIS6:
Tags: HttpHandler, IIS6, ASP.NET
Theme by Codeblack
I'm a .NET Architect with Quintor in Groningen, The Netherlands. I work with .NET, C#, SQL Server, etcetera. I'm also involved in ALM using Visual Studio and Team Foundation Server.