Geek Answers Handbook

Combres.axd returns 404 in a WebForms application

I have 2 ASP.NET applications, 1 WebForms and 1 MVC. Combres worked great for both, working locally on IIS Express. After deploying both applications on the test server (IIS 7, both applications are on the same website in IIS), the combres.axd link, which is referenced in the pages of the WebForms application, returns 404, while the MVC application works fine.

I connected the WebForms application to my local IIS and it worked fine again.

I looked at the modules and handlers between my local IIS, MVC application, and WebForms application, and the routing registration was the same.

If I set defaultDebugEnabled = "true", then it generates a script tag for each script in the resource set and works fine.

Any ideas on debugging 404 from combres.axd?

+4
webforms routing combres
source share
1 answer

Track it to the configuration of the modules in the web.config file:

<system.webServer> <modules runAllManagedModulesForAllRequests="true"/> </system.webServer>

I am working with an outdated WebForms application created around .NET 3.0 / 3.5, so I did not have the runAllManagedModulesForAllRequests attribute set. I see ASP.NET WebForms in the latest Visual Studio 2010 template, now this is the default value.

I also found a post suggesting a less brute force method to get an UrlRoutingModule to catch the combres.axd route.

 <system.webServer> <modules> <remove name="UrlRoutingModule-4.0" /> <add name="UrlRoutingModule-4.0" type="System.Web.Routing.UrlRoutingModule" preCondition="" /> </modules> </system.webServer>

One update mentioned this update, but I have not tested it yet:

http://support.microsoft.com/kb/980368

+3
source share

More articles:


All Articles