IIS eurl.axd Error File Not found
July 15, 2010
Posted by on
Finally after weeks trying to resolve my issue with the eurl.axd when I upgraded to the .net 4.0 framework. I was able to get on the phone with Microsoft to resolve the issue.
We spent about 45 minutes on the phone discussing the setup and a little bit of how IIS works under the hood.
When a request comes into IIS and the requested URL does not have a file extension, IIS in the early stages of the request appends /eurl.axd/guid/ to the URL. Where guid is unique to the life time of the application (and possible the life of the app pool). So what I had done was configure a second website with multiple host headers and “Home Directory” tab specifying a redirect to URL instead of a folder as normally would be done. The request has not yet reached the ASP.net filter or extension that would handle the request for .axd files, but it read the Metabase configuration to see if it needs to redirect, when it does it fails to remove the eurl.axd from the “appended” original request. In the process it just says ok, new URL specified in the configuration plus the path to the file that was requested, but we didn’t request eurl.axd, and it never removes it from the request.
- not sure why it appends the value to the URL without first checking to see if it needs to redirect.
- not sure why the redirect works that way when the “description” says this specific URL. It doesn’t say this specific URL and this Folder/File.
So what we did to resolve it was, change the redirect website to the 2.0 framework even though no code is executed on it. Thank goodness that it didn’t affect having to change back to 2.0 framework on the real site, I like having the ability to remove things from the viewstate with such level of control.