1
Vote

Can't revert back after applying to legacy app

description

We experimented with adding FriendlyUrls to a legacy app, but found it caused problems.
In Dev Env we run in local IIS and map a virtual directory...
We removed all references to the friendly URL code... no longer calling routes.EnableFriendlyUrls, but it appears URL is still getting "rewritten" and then the default handler is no longer able to find the requested resource.

If I change the mapped virtual directory, it works.

Even deleting the previous website, and deleting the temporary gen'd files, the request still is being "rewritten" with the ".aspx" removed from the request and mapped to System.Web.Handlers.TransferRequestHandler.

If I include a query string, or simply append "/" to the request address, so it is "site/mypage.aspx/", the request is not modified and is passed directly using the compiled page as its handler.

So the problem is... once we apply friendly URLs to a virtual directory, we can no longer use that virtual directory name.

Yes... we have run IIS reset. Still no love.

Any ideas?

comments

blairstark wrote Jan 11, 2016 at 6:05 AM

PLEASE!!!!!

is there anything I can provide to get this addressed? It is of the utmost urgency.

Here is all you have to do to duplicate,

Create a website using friendly URLs.
Map it to a local iis site, such as http://localhost/friendlyurls Run the app, it works fine.
Remove the friendly URL package, cleanup all references to friendly URLs.

Run the app... doesn't work, it appears the URL rewritter is left in place , as the URL still doesn't have ,aspx, but there is no handler for it,

How do I remove the URL rewritter ?

I really need help with this. My boss is losing patience with me!

pcdonp wrote Mar 25 at 8:33 PM

Maybe the issue comes from browser cache? Once the browser receives a HTTP 301 (moved permanently) status code, it will keep on requesting the friendly URL, which is not available any more after reverting to legacy app.