Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

ASP.NET MVC on IIS 6 - wildcard mapping - the incoming request does not match any route

I have been trying to set up my Beta 1 MVC app on IIS 6 and cannot get it to run correctly. I have added a Wildcard mapping to the .net isapi DLL as suggested in other blog posts but get the following error when I access the root of the website:

The incoming request does not match any route.
..
[HttpException (0x80004005): The incoming request does not match any route.]
   System.Web.Routing.UrlRoutingHandler.ProcessRequest(HttpContextBase httpContext) +147
   System.Web.Routing.UrlRoutingHandler.ProcessRequest(HttpContext httpContext) +36
   System.Web.Routing.UrlRoutingHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context) +4
   HCD.Intranet.Web.Default.Page_Load(Object sender, EventArgs e) +81
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

I am using the Default.aspx page supplied in the MVC template application that rewrites access to the root of the website properly.

public partial class Default : Page
{
    public void Page_Load(object sender, System.EventArgs e)
    {
        HttpContext.Current.RewritePath(Request.ApplicationPath);
        IHttpHandler httpHandler = new MvcHttpHandler();
        httpHandler.ProcessRequest(HttpContext.Current);
    }
}

If I try and access a route within the application, such as /Project, I get the standard IIS 404 error page, not the .net error page.

I tried adding the following line to my Web.config httpHandlers section:

<add verb="*" path="*" validate="false" type="System.Web.Mvc.MvcHttpHandler, System.Web.Mvc, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

This gave me a different error - the .net 404 error page.

I added the following to my Global.asax, which did nothing:

protected void Application_BeginRequest(object sender, EventArgs e)
{
    if (Context.Request.FilePath.Equals("/"))
        Context.RewritePath("Default.aspx");
}

I am using the following route configuration (uses the restful routing supplied by the MvcContrib project):

routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
SimplyRestfulRouteHandler.BuildRoutes(routes);
routes.MapRoute(
"Default", 
"{controller}/{action}/{id}",
new { controller = "Home", action = "Index", id = "" }
);

Any suggestions would be grealy received as I've exhausted all options for the time I have right now.

Many thanks.

like image 958
Tim Peel Avatar asked Nov 09 '08 13:11

Tim Peel


People also ask

Can I migrate wildcard script mapping from IIS 6 to IIS 7?

This post explains how an application that used wildcard script mapping in IIS 6 can be migrated over to IIS 7 and above. Assume you had configured ASP.NET in IIS 6 to handle all requests by using wildcard script mapping. For example you had an ASP.NET module for URL rewriting and you wanted this module to handle extension-less URLs.

Can I run MVC on IIS 6?

UPDATE: If you run ASP.NET MVC on IIS 6 with ASP.NET 4, setting up extensionless URLs just got easier . In most cases, it should just work. I’ve seen a lot of reports where people have trouble getting ASP.NET MVC up and running on IIS 6. Sometimes the problem is a very minor misconfiguration, sometimes it’s a misunderstanding of how IIS 6 works.

How to host ASP NET MVC web application on local IIS?

How To Host ASP.NET MVC Web Application on Local IIS 1 Move the published code on Hosting Server. ... 2 Open IIS Manager. ... 3 Add Website to host an ASP.NET MVC application. ... 4 Define Site Name & Application Pool. ... 5 Browse and select Published Folder path. ... 6 Define IP address & Port. ... More items...

How does IIS 6 handle ASP NET requests?

ASP.NET was plugged into IIS 6 as an ISAPI extension and by default was configured to handle ONLY requests mapped to that extension - for example any request that ended with ".aspx" would be processed by the ASP.NET extension.


1 Answers

Here's what I did to get extensionless URLs working with IIS 6 and ASP.NET MVC Beta 1.

  • Create a default ASP.NET MVC Beta project and compile it.
  • Create a new IIS website pointing to the application directory.
  • In the IIS properties for the website, click the HomeDirectory tab.
  • Click the "Configuration..." button. In the "Mappings" tab, click "Insert..."
  • Next to the "Wildcard application maps" label In the textbox, type in "c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll"
  • Uncheck the box labelled "Verify that file exists" Click OK
  • Navigate to /home It worked!

You shouldn't need to change web.config at all. You just need to map all requests to IIS to the ASP.NET Isapi dll otherwise ASP.NET will never get those requests.

like image 164
Haacked Avatar answered Sep 27 '22 20:09

Haacked