Shulou(Shulou.com)06/03 Report--

This article mainly introduces the differences between URL Routing in ASP.NET and URL Rewriting on IIS. What is introduced in this article is very detailed and has a certain reference value. Interested friends must read it!

Examples

Before analyzing the principle, let's do an example test (the IIS URL Rewrite module needs the support of IIS7).

1. Establish the corresponding MVC program for the URL of Customer/1

First, create a common MVC3 program, a simple CustomerController and a simple Detail action, the code is as follows:

Public class CustomerController: Controller {public ActionResult Detail (string id) {ViewBag.CustomerID = id; return View ();}}

We simply accept an ID and put it in ViewBag to display in view. The code for view is as follows:

@ {Layout = null;} run under Detail MVC result: @ ViewBag.CustomerID

two。 Establish the corresponding web form program for the URL of Customer/1

Under the root directory of the same solution, create a Customer.aspx file. The file code mainly accepts an ID parameter and displays it on the page. The code:

Public partial class Customer: System.Web.UI.Page {protected void Page_Load (object sender, EventArgs e) {this.lblId.InnerText = Request.QueryString ["id"];}}

Html:

Under asp.net web form are:

OK, let's configure the route of Customre/1 in Global.asax.cs as follows:

Routes.MapRoute ("CustomerDetail", / / Route name "Customer/ {id}", / / URL with parameters new {controller = "Customer", action = "Detail", id = UrlParameter.Optional})

Compile access, run http://localhost/customer/123, and the page displays the result as follows:

The result of running under MVC: 123.

3. Install IIS URL Rewrite

After downloading and installing IIS URL Rewrite, http://www.iis.net/download/URLRewrite at the following address, configure a URL rewriting rule in the web.config of the MVC project as follows (note that it is the system.webServer node):

The rule means that a request similar to customer/1 is rewritten to customer.aspx?id=1, and the compiler accesses the following http://localhost/customer/123, and the page displays the following result:

Under asp.net web form: 123

In other words, Routing doesn't work at this time, because URL Rewrite forwards the address of Customer/123 to Customer.aspx?id=123 before Routing, and the aspx file receives the request. Let's take a look at the cycle in which the two are processed.

Principle period

1. URL Rewrite

About URL Rewrite first seen in apache web server, at that time popular url rewriting made a large number of people using php ecstatic ah, unfortunately, because the implementation of asp.net is particularly complex, so many stations are basically not used, since IIS.net launched the formal IIS URL Rewrite module, completely solved this problem.

URL Rewrite is executed in the early stage of request-processing pipeline. Generally, after an address comes in, the module will map to another new address on the same server according to the rules. The parameters and data accepted by the new address are judged by the parameters of a new address, such as customer.aspx?id=123, and the url in request is also a new address, rather than rewriting the previous address. However, users themselves do not feel the change, because the browser has been showing the old URL, let's take a look at its cycle chart.

URL Rewrite module is a module of native. From the figure, we can see that its running cycle is between Pre-begin Rquest and Begin Request. After matching rules according to the requested URL, the module finally processes the new URL so that it can be processed in the rest of the IIS pipeline cycle, that is, the HttpHandler that handles the request is determined according to the new URL after rewriting.

2. URL Routing

The principle of URL Routing is to define rules according to the existing URL, and to define the HttpHandler corresponding to each rule. Its nature has nothing to do with whether the URL is friendly or not. It just invokes the corresponding HttpHandler according to the unified rules, finds the corresponding HttpHandler, and returns the result after processing. If you can't find it, you will expose the resource error.

Routing is a managed code module that is registered in the Resolve Cache cycle (PostResolveRequestCache event) and then processed in the MapHandler cycle. In the PostResolveRequestCache event, the module queries the URL matching rules declared in all records in the static set routing table, and if the current URL corresponds to a matching Handler, it then uses that Handler to process the results and output.

The difference between the two

Whether URL Rewrite modifies the corresponding URL,URL Rewrite module before request processing does not know which HttpHandler handles the request, and the HttpHandler handling the request does not know whether the URL it is dealing with is the original URL or the rewritten address.

In contrast to URL Rewrite, URL Routing specifies HttpHandler for URL according to the rules, which can be thought of as a high-level mapping of handler.

IIS URL Rewrite can be used for mapping processing of any web program, including, but not limited to, asp.net,php,asp and static files, but Routing can only handle. Net-based web programs.

IIS URL Rewrite can be used in both IIS integration mode and classic mode, but by default Routing can only be used in integrated mode. In classic mode, you need to use an extension or wildcard to map the program to IIS (in fact, .net has another component aspnetfilter has already done for us).

IIS URL Rewrite can handle rewriting rules based on domain names, paths, Http Header,server variables, etc., but Routing can only handle rewriting rules according to the requested URL path and HTTP-Method header.

IIS URL Rewrite can handle HTTP jumps, custom Status Code and Abort requests, but Routing can't.

IIS URL Rewrite's extension can only extend its own Provider to customize the storage of rules, but Routing's extension is relatively powerful, and MVC is one of them.

The above is all the content of this article entitled "what is the difference between URL Routing in ASP.NET and URL Rewriting on IIS". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.