Skip to main content

URL rewritting

A URL Rewriting


This article describes a complete solution for URL rewriting in ASP.NET 2.0. The solution uses regular expressions to specify rewriting rules and resolves possible difficulties with postback from pages accessed via virtual URLs.

Why should we use URL rewriting?


The two main reasons to incorporate URL rewriting capabilities into your ASP.NET applications are increased usability and easy to maintain

(1)increased usability


It is well-known that users of web applications prefer short, neat URLs to monstrous addresses packed with difficult to comprehend query string parameters. From time to time, being able to remember and type in a concise URL is less time-consuming than adding the page to a browser's favorites only to access later. Again, when access to a browser's favorites is unavailable, it can be more convenient to type in the URL of a page on the browser address bar, without having to remember a few keywords and type them into a search engine in order to find the page.
Compare the following two addresses and decide which one you like more:
(1) http://www.zombie.com/Blogs/lastest.aspx?yy=2008&mm=08&dd=20

(2) http://www. Zombie.com/Blogs/2008/08/20/
As we can see the first url is little descriptive and it is useless to remember for end user who is browsing your site, so second one is defined, it can be clearly seen that second one is much better to read and useable.

(2)Easy to maintain


It is very common scenario in web world that changes are taken place each and every day in our developer life, say we have page called contactus.aspx in contact folder and tos.aspx in terms folder but later we decide to move both the pages on static Content folder ,now if any one has book marked our page will get an error stating that page is not there(As we have moved it), so for that purpose also this rewriting is useful, We can make changes in our config file and maintain it very easily, By this we can see clear separation between physical structure and logical structure of stored files.

URL mapping from web.config


ASP.NET 2.0 provides an out-of-the-box solution for mapping static URLs within a web application. It is possible to map old URLs to new ones in web.config without writing any lines of code. To use URL mapping, just create a new urlMappings section within the System.web section of your web.config file and add the required mappings (the path ~/ points to the root directory of the web application):
Thus, if a user types http://www.zombie.com/contact/contact.aspx, he can then see the page located at http://www.zombie.com/staci/contact.aspx.

ZOMBIE:NOTE: This is solution is good where there are small amount of pages moved to directories, but what if there are plenty of pages that have been moved away here and there??? So content for the same is coming soon stay tuned…..

Comments

Post a Comment

Popular posts from this blog

One or more exceptions occurred while processing the subscribers to the 'item:creating' event

I was recently installing the packages from one of the QA environment to my local Sitecore instance, "Media library package" to be precise, And it started giving me this below error One or more exceptions occurred while processing the subscribers to the 'item:creating' event Looking at the sitecore logs, it gave me more info on the context and the actual inner exception was following Solution: 'Name' should consist only of letters, digits, dashes or underscore Now it was evident that some of my file names were violating the naming rule, I could see in the log just before exception from where the installer stopped creating items, and that file name had round braces "(" and ")" at the end of it, with my surprise I was able to create the item with those name in the content tree, but below was the solution for it, Solution I am using SC 9.0.1 and in that Go to Sitecore.Marketing.config file residing in "App_Config\Sitecore\Mar...
9 comments
Read more

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...
2 comments
Read more

Error in Sitecore 10.3 XM with CDs - Could not find configuration node: database/database[@id='master']

Hi Team, Recently we came across two distinct scenarios with same error message.  1) We started getting below error when we try to hit our layout service API endpoint. If we hit end point of CM, it was working fine and when we try to hit end point of CD it was giving this error, It was clear there is something in backend expecting master DB instead of WEB DB In first scenario my colleague  Jatin  also got same issue while setting up docker instance for 10.3, and my friend  Akshay Barve  and I had the same observation. 2) Second scenario I was having the same exception, It was another project on 10.3 XM with CD, It was one of the migration project so we were migrating from 10.2 to 10.3, Older site was not giving any error but new site the moment we hit, it was giving same exception in the log Issue in second scenario was in site grouping there was only site and both CM and CD URLs were given in host name and had WEB db as database, so basically there was no previ...
Post a Comment
Read more