Differences between iis url rewriting and asp.net routing
Upcoming SlideShare
Loading in...5

Differences between iis url rewriting and asp.net routing



Differences between IIS URL Rewriting and ASP.NET Routing

Differences between IIS URL Rewriting and ASP.NET Routing



Total Views
Slideshare-icon Views on SlideShare
Embed Views



1 Embed 2

http://www.pinterest.com 2



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Differences between iis url rewriting and asp.net routing Differences between iis url rewriting and asp.net routing Document Transcript

    • Differences between IIS URL Rewriting and ASP.NET Routing S.No URL Rewriting ASP.NET Routing 1 Meaning: Meaning: URL rewriting consists of ASP.NET routing extracts specific certain regular expression values from the URL, based on a patterns that match an pattern. These extracted values incoming request URL and can be used to determine the forward the request to a handler that will handle the mapped URL instead. For request. We can also use these example, one might create a patterns to generate a URL that will URL rewriting rule that map to a specific handler. forwards an incoming request for http://www.example.com/Produ cts/Beverages to another URL of http://www.example.com/Produ cts/Show.aspx?id=5 2 Does it alter the request / Does it alter the request / incoming URL ? incoming URL ? URL rewriting alters the ASP.NET routing is different. It request URL and forwards it to does not alter the incoming URL. another URL. 3 When URL Rewriting is right When ASP.NET Routing is right choice ? choice ? IIS URL rewriting is a generic ASP.NET routing is a solution that URL manipulation mechanism is optimized for ASP.NET, thus it that addresses a multitude of may be preferable for Web scenarios. In particular, it can developers who design their be used by Web developers as ASP.NET applications from the well as Web server/site ground up and want to have a administrators to enable clean clean URL structure. URLs for existing Web applications without modifying the application code. 4 For what type of For what type of application(s) application(s) URL Rewriting ASP.NET Routing can be used ? can be used ? ASP.NET routing can be used only The IIS URL Rewrite module with .NET Framework-based Web can be used with any type of applications. Web application, which includes ASP.NET, PHP, ASP, and static files. 5 Does it extensible and Does it extensible and customizable ? customizable ?
    • The URL Rewrite module is not ASP.NET routing is fully extensible extensible in its current and customizable. version. 6 What tasks it can perform ? What tasks it can perform ? In addition to rewriting, the ASP.NET routing does not perform URL Rewrite module can these tasks. perform HTTP redirection, issue custom status codes, and abort requests. 7 Application Area: Application Area: The IIS URL Rewrite module By default, ASP.NET routing works can make rewriting decisions only with URL paths and with the based on domain names, HTTP-Method header. HTTP headers, and server variables. 8 IIS pipeline mode or IIS pipeline mode or Integrated Integrated pipeline mode ? pipeline mode ? The IIS URL Rewrite module For ASP.NET routing, it is works the same way preferable to use integrated regardless of whether pipeline mode. ASP.NET routing integrated or classic IIS can work in classic mode, but in pipeline mode is used for the that case the application URLs application pool. must include file name extensions or the application must be configured to use "*" handler mapping in IIS.Summary:IIS Rewiting & ASP.NET Routing:"Either IIS URL rewriting or ASP.NET routing can be used to implement URL manipulationscenarios for your Web application. " - By Ruslan YakushevMain advantage of ASP.NET Routing:It keeps the request-resource resolution logic within your application, so its very easy toadd application-dependent logic when you need, and it eliminates the need to maintainsynchronization between your application and a separate configuration resource.Routing works great with traditional webforms.References:http://my.safaribooksonline.com/book/web-development/microsoft-aspdotnet/9781847197542/routing/ch05lvl1sec02http://www.iis.net/learn/extensions/url-rewrite-module/iis-url-rewriting-and-aspnet-routinghttp://seow3c.blogspot.in/2012/04/differences-between-iis-url-rewriting.html
    • http://stackoverflow.com/questions/915771/url-rewriting-vs-routingAnd, further updates on difference between questions and answers, please visit myblog @ http://onlydifferencefaqs.blogspot.in/