Archive for June, 2010

301 Redirect

301 redirect is the most efficient and Search Engine Friendly method for webpage redirection. It’s not that hard to implement and it should preserve your search engine rankings for that particular page. If you have to change file names or move pages around, it’s the safest option. The code “301” is interpreted as “moved permanently”.

You can Test your redirection with Search Engine Friendly Redirect Checker

Below are a Couple of methods to implement URL Redirection

IIS Redirect

1. Server -> run -> Inetmgr [iis]

2. Right click a domain that you want to redirect -> properties

3.

Choose home directory

4. Select redirection to the URL and enter the URL in the text box

5. Apply and press ok. Thats all. iisreset to reflect the changes if its not working.

ColdFusion Redirect

<.cfheader statuscode=”301″ statustext=”Moved permanently”>
<.cfheader name=”Location” value=”http://www.new-url.com”&gt;

PHP Redirect

<?
Header( “HTTP/1.1 301 Moved Permanently” );
Header( “Location: http://www.new-url.com&#8221; );
?>

ASP Redirect

<%@ Language=VBScript %>
<%
Response.Status=”301 Moved Permanently”
Response.AddHeader “Location”,”http://www.new-url.com/&#8221;
%>

ASP .NET Redirect

<script runat=”server”>
private void Page_Load(object sender, System.EventArgs e)
{
Response.Status = “301 Moved Permanently”;
Response.AddHeader(“Location”,”http://www.new-url.com&#8221;);
}
</script>

JSP (Java) Redirect

<%
response.setStatus(301);
response.setHeader( “Location”, “http://www.new-url.com/&#8221; );
response.setHeader( “Connection”, “close” );
%>

CGI PERL Redirect

$q = new CGI;
print $q->redirect(“http://www.new-url.com/&#8221;);

Ruby on Rails Redirect

def old_action
headers[“Status”] = “301 Moved Permanently”
redirect_to “http://www.new-url.com/&#8221;
end

Redirect Old domain to New domain (htaccess redirect)

Create a .htaccess file with the below code, it will ensure that all your directories and pages of your old domain will get correctly redirected to your new domain.
The .htaccess file needs to be placed in the root directory of your old website (i.e the same directory where your index file is placed)

Options +FollowSymLinks
RewriteEngine on
RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

Please REPLACE http://www.newdomain.com in the above code with your actual domain name.

In addition to the redirect I would suggest that you contact every backlinking site to modify their backlink to point to your new website.

Note* This .htaccess method of redirection works ONLY on Linux servers having the Apache Mod-Rewrite moduled enabled.

Redirect to www (htaccess redirect)

Create a .htaccess file with the below code, it will ensure that all requests coming in to domain.com will get redirected to http://www.domain.com
The .htaccess file needs to be placed in the root directory of your old website (i.e the same directory where your index file is placed)

Options +FollowSymlinks
RewriteEngine on
rewritecond %{http_host} ^domain.com [nc]
rewriterule ^(.*)$ http://www.domain.com/$1 [r=301,nc]

Please REPLACE domain.com and http://www.newdomain.com with your actual domain name.

Note* This .htaccess method of redirection works ONLY on Linux servers having the Apache Mod-Rewrite moduled enabled.

How to Redirect HTML

Please refer to section titled ‘How to Redirect with htaccess’, if your site is hosted on a Linux Server and ‘IIS Redirect’, if your site is hosted on a Windows Server.

Type the following code and save it as index.php

<?php

   header( 'Location: http://www.yoursite.com/new_page.html' ) ;

?>

In the location section, add the domain that you want to redirect it. For example, if you have a.com and want it to redirect it to b.com, type b.com in the location section.

more info from here:-

http://www.webconfs.com/how-to-redirect-a-webpage.php

MICROSOFT GUIDE – translate-htaccess-content-to-iis-webconfig

http://learn.iis.net/page.aspx/557/translate-htaccess-content-to-iis-webconfig/
http://learn.iis.net/page.aspx/557/translate-htaccess-content-to-iis-webconfig/

Advertisements

http://skullboxx.net/kb/node/200

http://skullboxx.net/kb/node/199

Although its not increasing the maximum remote desktop protocol (RDP) connection but here are the few tips worth posting.

1. If the “maximum number of users exceeded” [error] while connecting a domain you can try:
run -> mstsc /console -> server login credentials

2. Enable user can connect with same login twice [something like that] in Administrative tools -> Terminal services configuration
—I have tried this in Windows 2008 server