IIS 7 and Above
Failed to Execute Url (System.Web.DefaultHttpHandler.BeginProcessRequ...
Last post May 07, 2008 11:22 AM by ldefreitas
May 07, 2008 11:22 AM|ldefreitas|LINK
I have the same problem, that is :
I have follow the instuction to make the wildcard to ASP.Net, by adding this code on web.config:
<add name="Wildcard" path="*" verb="*" modules="IsapiModule" resourceType="Unspecified"
After that, the wildward works but my "page" does not render any of image and no ressources is loaded (css, js...).
When i put directly the URL of an image for instance, I have the "Failed to Execute URL". The problem is inside the DefaultHttpHandler that is the default handler for files that is not directly managed by ASP.Net
I have just understood that DefaultHttpHandler try to redirect the request to IIS and it is not allowed in IIS7. This behavior allow to server page that need other ISAPI filters (like .asp, .php, .exe, .dll, and so on).
If you don't need this behavior but just need to serve static files (jpg, css, js...), you can add this lines to web.config:
<remove path="*" verb="GET,HEAD,POST" />
<add path="*" verb="GET,HEAD,POST" type="System.Web.StaticFileHandler" validate="True" />
This consist to remove the DefaultHttpHandler for all non managed ressources to the StaticFileHandler.
It works for me.