View Single Post
Old April 10th, 2009, 02:05 PM
stefsch stefsch is offline
Wrox Author
Join Date: Feb 2006
Location: Redmond, Washington, USA.
Posts: 76
Thanks: 0
Thanked 0 Times in 0 Posts

Wildcard mapping doesn't cause double execution of .aspx because .aspx is already handled by the ASP.NET ISAPI extension. The problem with modifying the response when using wildcard mappings only occurs when there is something other than ASP.NET that expects to work with the response data after ASP.NET runs. Classic ASP is a good example since it has its own ISAPI extension that expects to have exclusive access to response data.

As you noted below, when an anonymous user first tries to access non-ASP.NET content (i.e. foo.asp) - and wildcard mapping is in effect - and ASP.NET has UrlAuthorization turned on - the redirect triggered by authorization failure immediately ends the request. At that point ASP.NET sends a redirect the response ends. So the request never gets passed back out of ASP.NET and over to classic ASP.