Which url rewriter do you use for ASP.Net?

Question

I looked through several rewriting URLs for ASP.Net and IIS and wondered what everyone else was using and why.

Here are the ones I used or watched:

• ThunderMain URLRewriter : used in the previous project, it did not have the flexibility / performance we were looking for
• Ewal UrlMapper : used in the current project, but the source seems abandoned
• UrlRewritingNet.UrlRewrite : It seems like a decent library, but the documentary bad grammar leaves me feeling uneasy.
• UrlRewriter.NET : this is my current fav, it has a lot of flexibility, although additional functions that are downloaded to replace regular expressions change the standard. Pure regex syntax
• Managed by Fusion URL Rewriter : I found this in a previous question on stack overflow, but have not tried it yet, from the syntax of the example, it cannot be edited through web.config

Answer 1

+1 UrlRewritingNET.URLRewrite - used in several hundred services / portals / sites on one box without any problems for many years! (@Jason is the one you're talking about, isn't it?)

and I also used URLRewriter.NET on a personal site and found it, oh, interesting. @travis, you're right about the changed syntax, but once you get used to it, that’s good.

Answer 2

There is System.Web.Routing, which was just released with .NET 3.5.

You can simply use Request.RewritePath () in your custom HttpModule

I prefer to use the IHttpHandlerFactory implementation and have full control over all incoming URLs and where they are mapped.

Answer 3

If I were starting a new web project, I would look at using MVC from scratch. It uses rewritten URLs as standard.

Answer 4

IIS 7 has a URL Rewrite Module that is robust enough and integrates well with IIS.

Answer 5

I used UrlRewriting.NET before on a site with very high traffic - it worked great for us. I think the developers are German, so the English documentation is probably not as good as it could be. I would highly recommend it.

Answer 6

I had good experience with the Ionic ISAPI Rewrite Filter , which is very similar to ISAPI_Rewrite, except for free ones. Both models are modeled after mod_rewrite and are ISAPI filters, so you cannot control them in code, because you must install them in IIS.

Answer 7

I would not recommend UrlRewritingNet if you are in IIS7 Windows 2008.

Reason: UrlRewritingNet requires you to use application pool mode = classic and NOT integrated. This is not optimal. In addition, their project seems very dead that last 2 years.

Answer 8

I just installed Helicon ISAPI Rewrite 3 . It works just like htaccess. I am still satisfied.

Answer 9

I have used the .NET URL Rewriter and Reverse Proxy with great success. This is almost on par with mod_rewrite and uses almost all of the same syntaxes. The project owner is extremely helpful and friendly, and the product works great. This pearl provides rewriting and proxy features that many solutions do not offer. IMO, it's worth a look.

Answer 10

+1 for UrlRewritingNet.Url Register, but why do I always need to end my URL with .aspx? I think this should improve the improved regular expression.

Why do I always have to end up with aspx in virtualURL localhost / Products / Beverages.aspx "," localhost / Products / Condiments.aspx ". I just want to type localhost / Products / Beverages", "localhost / Products / Condiments" that look like route MVC.

This one looks good, but it doesn’t work on my site. I still can not understand.

Answer 11

asp.net routing also fulfills the requirement of rewriting URLs, and even much more. With asp.net routing, you cannot just "rewrite URLs", but create custom handlers for various requests. However, asp.net routing requires at least asp.net sp1.

The main thing you do for simple routing work is to add several route handlers to Application_Start even inside the Global.asax.cs file.

protected void Application_Start(object sender, EventArgs e) { RegisterRoutes(RouteTable.Routes); } private static void RegisterRoutes(RouteCollection routes) { routes.Add("Routing1", new Route("/Blog/id/2","/Blog.aspx")); }