Dots in URL causes 404 with ASP.NET mvc and IIS

I got this working by editing my site’s HTTP handlers. For my needs this works well and resolves my issue.

I simply added a new HTTP handler that looks for specific path criteria. If the request matches it is correctly sent to .NET for processing. I’m much happier with this solution that the URLRewrite hack or enabling RAMMFAR.

For example to have .NET process the URL add the following line to your site’s web.config within the system.webServer / handlers element:

<add name="ApiURIs-ISAPI-Integrated-4.0"
     preCondition="integratedMode,runtimeVersionv4.0" />


There are other posts suggesting that the solution to this issue is RAMMFAR or RunAllManagedModulesForAllRequests. Enabling this option will enable all managed modules for all requests. That means static files such as images, PDFs and everything else will be processed by .NET when they don’t need to be. This options is best left off unless you have a specific case for it.

Leave a Comment