IIS 7 Not Serving Default Document

iis-7.5

We have a problem occuring on some of our developer workstations: when visiting a URL without a filename (e.g. http://localhost/), IIS 7 returns a 404 error. Everyone is running Windows 7/IIS 7.5 and ASP.NET 4.0. The application pool is configured to use Classic pipeline mode.

Default documents are enabled, and default.aspx is in the default document list.

I enabled failed request tracing, and see this in the log:

OldHandlerName="", NewHandlerName="ExtensionlessUrl-ISAPI-4.0_64bit", 
  NewHandlerModules="IsapiModule", 
  NewHandlerScriptProcessor="C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll", NewHandlerType=""

Later on, I see that this IsapiModule is rejecting the request:

ModuleName="IsapiModule", Notification="EXECUTE_REQUEST_HANDLER", HttpStatus="404",
  HttpReason="Not Found", HttpSubStatus="0", 
  ErrorCode="The operation completed successfully. (0x0)", ConfigExceptionInfo=""

It looks like IIS thinks the ExtensionlessUrl-ISAPI-4.0-64bit should be handling the request. When I look at that module's configuration, it shows that it should be matching path *., so I'm confused why it is matching no path.

A Google search turns up this post on the IIS.net forums from 2005. Unfortunately, no solutions are offered, just an acknowledgement of the problem.

When I update my app pool to use integrated mode, the problem goes away. Unfortunately, it has to run in Classic mode.

What can I do to get IIS to server our default documents again?

Best Answer

It looks like Microsoft released an update that enables the ExtensionlessURL HTTP handler to work with extensionless URLs. Unfortunately, this breaks certain other handlers. In my case, the DefaultDocument handler under classic app pools. The solution is to remove the ExtensionlessURL handlers in our application's web.config:

<system.webServer>
  <handlers>
    <remove name="ExtensionlessUrl-ISAPI-4.0_32bit" />
    <remove name="ExtensionlessUrl-ISAPI-4.0_64bit" />
    <remove name="ExtensionlessUrl-Integrated-4.0" />
  </handlers>
</system.webServer>

Related Solutions

ASP.NET MVC on IIS 7.5

ASP.NET 4 was not registered in IIS. Had to run the following command in the command line/run

32bit (x86) Windows

%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir

64bit (x64) Windows

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir

Note from David Murdoch's comment:

That the .net version has changed since this Answer was posted. Check which version of the framework is in the %windir%\Microsoft.NET\Framework64 directory and change the command accordingly before running (it is currently v4.0.30319)

IIS 7.5 routing not working (all usual methods tested)

My solution, after trying EVERYTHING:

Bad deployment, an old PrecompiledApp.config was hanging around my deploy location, and making everything not work.

My final settings that worked:

IIS 7.5, Win2k8r2 x64,
Integrated mode application pool

Nothing changes in the web.config - this means no special handlers for routing. Here's my snapshot of the sections a lot of other posts reference. I'm using FluorineFX, so I do have that handler added, but I did not need any others:

<system.web>
  <compilation debug="true" targetFramework="4.0" />
  <authentication mode="None"/>

  <pages validateRequest="false" controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"/>
  <httpRuntime requestPathInvalidCharacters=""/>

  <httpModules>
    <add name="FluorineGateway" type="FluorineFx.FluorineGateway, FluorineFx"/>
  </httpModules>
</system.web>
  <system.webServer>
    <!-- Modules for IIS 7.0 Integrated mode -->
    <modules>
      <add name="FluorineGateway" type="FluorineFx.FluorineGateway, FluorineFx" />
    </modules>

    <!-- Disable detection of IIS 6.0 / Classic mode ASP.NET configuration -->
    <validation validateIntegratedModeConfiguration="false" />
  </system.webServer>

Global.ashx: (only method of any note)

void Application_Start(object sender, EventArgs e) {
    // Register routes...
    System.Web.Routing.Route echoRoute = new System.Web.Routing.Route(
          "{*message}",
        //the default value for the message
          new System.Web.Routing.RouteValueDictionary() { { "message", "" } },
        //any regular expression restrictions (i.e. @"[^\d].{4,}" means "does not start with number, at least 4 chars
          new System.Web.Routing.RouteValueDictionary() { { "message", @"[^\d].{4,}" } },
          new TestRoute.Handlers.PassthroughRouteHandler()
       );

    System.Web.Routing.RouteTable.Routes.Add(echoRoute);
}

PassthroughRouteHandler.cs - this achieved an automatic conversion from http://andrew.arace.info/stackoverflow to http://andrew.arace.info/#stackoverflow which would then be handled by the default.aspx:

public class PassthroughRouteHandler : IRouteHandler {

    public IHttpHandler GetHttpHandler(RequestContext requestContext) {
        HttpContext.Current.Items["IncomingMessage"] = requestContext.RouteData.Values["message"];
        requestContext.HttpContext.Response.Redirect("#" + HttpContext.Current.Items["IncomingMessage"], true);
        return null;
    }
}

Best Answer

Related Solutions

ASP.NET MVC on IIS 7.5

IIS 7.5 routing not working (all usual methods tested)

Related Topic