different in Response.RedirectPermanent method and Response.Redirect

ets say that I have a page called "page1.aspx", and  google cached it in his database search, now if I changed the page1.aspx or I removed it, then I need to put the Response.RedirectPermanent("Page2.aspx) in the page load of Page1.aspx, so that google next time will know that Page1.aspx has become Page2.aspx.

In the backend, http protocol supports 2 ways of redirections, 301 and 302. Permanant redirect send 301 response code to the browser

"301 redirects are permanent. They mean that the page has moved, and they request any search engine or user agent coming to the page to update the URL in their database. This is the most common type of redirect that people should use."


Response.RedirectPermanent  do the same thing as following code does.


        Response.Status = "301 moved permanently";
        Response.AddHeader("location", newPath);
        Response.End();



Response.RedirectParmanent
is an extension function introduced in .NET 4.0.
The main motive of it is to indicate the Response Code to the Search Engine that the page is moved permanently. The
Response.Redirect
generates Response code as 302 whereas
RedirectParmanent 
returns 301. 


Thus say you have a page, and which is included to search engine for a long time, if you use
Response.Redirect()
it will not change this effect to the search engine(taking this a temporary change), while if you use
Response.RedirectParmanent
()
it will take it as permanent. 


In case of
Server.Transfer()
the actual response is actually been updated. There is no effect to the search engine, and search engine will think the output is coming from the same page that is called upon. Let us give an example :


Say you have 2 pages (Page 1 and Page 2) where Page1 redirects to Page2
In case of 


1.
Response.Redirect()
: Search Engine will take this redirection as Temporary(Status 301) and always keep Page1 in its cache. 
2.
Response.RedirectParmanent
()
: Search Engine will take this a permanent redirection(Status 302) and will remove Page1 from its database and include Page2 for better performance on search.
3.
Server.Transfer()
: Search Engine will be unaware of any redirection been took place (Status 200) and will keep Page1 to its database. It will think Page1 is producing the output response of Page2.


When to use: 
Response.Redirect
is perfect when your page is temporarily changed and will be changed to original within a short span of time. 
Response.RedirectParmanent
()
when you are thinking of deleting the Page1 totally after the search engines changes its cache.
Server.Transfer()
when you are thinking of keeping the page for ever, and to let search engine unaware of this redirection. 



Comments

Post a Comment

Popular posts from this blog

Executing PowerShell scripts from C#

Image
Please refer the original post from here http://blogs.msdn.com/b/kebab/archive/2014/04/28/executing-powershell-scripts-from-c.aspx I n today’s post, I will demonstrate the basics of how to execute PowerShell scripts and code from within a C#/.NET applications. I will walk through how to setup your project prerequisites, populate the pipeline with script code and parameters, perform synchronous and asynchronous execution, capture output, and leverage shared namespaces. Update 8/7/2014 : Here is the downloadable solution file. Update 11/5/2014 : Added a section on execution policy behavior. Prerequisites: First, ensure that PowerShell 2.0 or later is installed on the system you are developing on. The features used below will not be supported on PowerShell 1.0. Next, start by making a new console application (targeting .NET 4.0) in Visual Studio. In the solution explorer, add a project reference to the System.Management.Automation assembly * . On my machine (PowerShe...
Read more

HOW TO Use the NumericUpDown Control

HOW TO Use the NumericUpDown Control  Great help taken from  http://www.asp.net/ajaxlibrary/HOW%20TO%20Use%20the%20NumericUpDown%20Control.ashx NumericUpDown Demonstration NumericUpDown Description NumericUpDown is an ASP.NET AJAX extender that can be attached to an ASP.NET TextBox control to add "up" and "down" buttons that increment and decrement the value in the TextBox. The increment and decrement can be simple +1/-1 arithmetic, they can cycle through a provided list of values (like the months of the year), or they can call a Web Service to determine the next value. Page authors can also provide custom images to be used instead of the default up/down button graphics. Video - How Do I: Use the ASP.NET AJAX NumericUpDown Control? NumericUpDown Client Code Sample view plain copy to clipboard print ? < script   runat = "server" >        [System.Web.Services.W...
Read more

Exposing Agile Software Development Myths

Agile development is a movement that started 11 years ago and now is a commonplace discussion for software development teams. Prior to the signing of the Agile Manifesto in Utah in 2001 [endnote 1], the world was using a phased methodology called “Waterfall,” introduced (but not named) by Winston W. Royce [2], ironically trying to explain why that methodology was a bad idea. The methodology forced the completion of a phase in order to continue with the next one. That caused some problems since, no matter how hard the developers tried to gather all requirements and create a full system design, there was always the need in the following phases to go back and change things. Those regressions had a big impact on cost. The Agile principles tried to eliminate all the rigidity of Waterfall by focusing on more productive tasks, like working code over comprehensive documentation, adding more customer collaboration, enforcing individual interactions instead of tools and being a...
Read more