#StackBounty: #asp.net #vb.net #iis #iis-8 #windows-server-2012-r2 IIS Classic Mode .NET Web API Call returns 404 Error

Bounty: 50

I have a pre-existing VB.NET web application running on IIS 8 in Windows Server 2012 R2. The application needs to handle a new API call (ex. localhost/test/ping) which I implemented using the APIController interface. I was able to successfully run the API call on my local Visual Studio, but once I deploy it to IIS, the url returns a 404 error.

After some digging and research, part of the problem I believe is the web app does not have ExtensionlessUrlHandler-Integerated-4.0 in the handler mapping. Looking into the configurations, apparently part of the pre-condition is the application cannot be me in classic mode, which mine is. I cannot switch to integrated mode which will break my app.

Is there a way around this limitation.


Update: Adding the web.config

<system.webServer>
  <modules runAllManagedModulesForAllRequests="true" />
  <handlers>
    <add name="MVC" path="*." verb="*" type="" modules="IsapiModule" scriptProcessor="C:WindowsMicrosoft.NETFrameworkv2.0.50727aspnet_isapi.dll" resourceType="File" requireAccess="None" allowPathInfo="false" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="4194304" />
  </handlers>
</system.webServer>


Get this bounty!!!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.