ASP.Net 1.1 wildcard gives 404 by default documents
I have an application that was asked to create a friendly url for a dynamic page that uses many query string values. After some research on the internet, I found that I need to create an HttpModule or HttpHandler to do the routing and then set up wildcard mapping in .Net v1.1 aspnet_isapi.dll in IIS (removing the Verify the File Exist checkbox).
Everything works fine on my XP Pro box using the virtual directory for testing.
When I promote it to a test environment (Server 2003), direct page access and routing stops working; however, the default document no longer works. I found a link online that says that IIS6 handles wildcard mapping to the default document logic due to the separation of ASP.Net WP and IIS6.
I tried to update my HttpHandler for the / route account; however, the code located in the routed pages no longer works. In Web.Config, I tried to use the path as * as well as / and get the same answer. I am also using Response.Redirect which is not correct in my opinion.
I have also tried URLRewriter.net; however, it didn't work after taking a few hours to get it working (it just won't route in this asp.net 1.1 application for some reason).
Any ideas as to what might be causing or how I can get my routes to the default page and my particular page setup, leaving the rest alone?
source to share
I found some typos in the README information for the URLRewriter. After setting it up based on the online documentation rather than the examples that come with the binaries, I was able to get it to work and solve the problem locally.
After I pushed the code to my test server, the suggested route works, but the default route is still not set. I changed the URL pattern for the default route a bit and it started.
source to share