• The List of Chat Acronyms & Text Message Shorthand

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

• In internet services manager, right click on the file or folder you wish to redirect
• Select the radio titled “a redirection to a URL”.
• Enter the redirection page
• Check “The exact url entered above” and the “A permanent redirection for this resource”
• Click on 'Apply'

<.cfheader statuscode="301" statustext="Moved permanently">
<.cfheader name="Location" value="http://www.new-url.com">

<?
Header( "HTTP/1.1 301 Moved Permanently" );
Header( "Location: http://www.new-url.com" );
?>

<%@ Language=VBScript %>
<%
Response.Status="301 Moved Permanently"
Response.AddHeader "Location","http://www.new-url.com/"
%>

<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");
}
</script>

<%
response.setStatus(301);
response.setHeader( "Location", "http://www.new-url.com/" );
response.setHeader( "Connection", "close" );
%>

$q = new CGI;
print $q->redirect("http://www.new-url.com/");

def old_action
headers["Status"] = "301 Moved Permanently"
redirect_to "http://www.new-url.com/"
end

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 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 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 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.

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

• How to move DokuWiki from one Server to another? [DokuWiki]
• plugin:wysiwyg [DokuWiki]
• faq:toolbar [DokuWiki]
• update_check [DokuWiki]
• Problem with Release 2011-11-10 "Angua RC1" "The mediaolddir ('media_attic') does not exist.."

  I had the same problem and I solved it by creating new directories (how was written before my post):
  /data/media_attic
  /data/media_meta

• Binaries of Apache 2.2.4 for Windows with OpenSSL 0.9.8e (mod_ssl) and mod_deflate support

To install, follow these steps:

1. Download apache_2.2.4-win32-x86-no_ssl.msi:

   wget http://www.apache.org/dist/httpd/binaries/win32/apache_2.2.4-win32-x86-no_ssl.msi

2. Install Apache:

   msiexec /i apache_2.2.4-win32-x86-no_ssl.msi

3. Stop Apache:

   net stop Apache2

4. Uninstall the Apache service:

   "C:\Program Files\Apache Group\Apache2\bin\httpd" -k uninstall

5. Kill the ApacheMonitor:

   taskkill /im apachemonitor.exe

6. Download apache-2.2.4_openssl-0.9.8e.zip.
7. Unzip into the directory you installed Apache in:

   unzip -o -d "c:/Program Files/Apache Group" apache-2.2.4_openssl-0.9.8e.zip

8. If you are using Cygwin's unzip, and are using NTFS, grant the SYSTEM user full rights to the Apache2 directory, as unzip may have removed them:

   cacls "C:\Program Files\Apache Group\Apache2" /E /G SYSTEM:F /T

9. Install Apache as a service with SSL support:

   "C:\Program Files\Apache Group\Apache2\bin\htttd" -D SSL -k install

10. And finally, start Apache:

    net start Apache2

To verify it's working, browse to https://127.0.0.1/. Since this is a self signed certificate, you will receive a message about an unknown certificate authority. Simply click 'Ok' and you should see Apache's standard welcome page.

Note: The .so files are actually Win32 DLL executables, they just have the standard Linux file extension.

• Running Apache as a Service - httpd -k install -n “MyServiceName” -f “c:\files\my.conf” ; httpd -k uninstall -n “MyServiceName” ; httpd -n “MyServiceName” -t ; httpd -k start|stop|shutdown|restart

• SSLSessionCache Directive - # none|nonenotnull|dbm:/path/to/datafile|shm:/path/to/datafile[(size)]|dc:UNIX:/path/to/socket

• Redirect port 80 to port 443 (ssl)

    RewriteEngine On
    RewriteCond  %{SERVER_PORT} !^443$
    RewriteRule ^(.*)$ https://www.domain.de/folder/$1 [L,R]

Cas de MAJ bloqué avec le message suivant:

Téléchargement de la mise à jour depuis http://fr.wordpress.org/wordpress-3.1.2-fr_FR.zip…

Décompression de la mise à jour…

Note: Cas rencontré avec XAMPP 1.7.3 en localhost

Il aurait suffi de mettre un temps d'execution plus long (par defaut dans mon cas, c'etait 60), et eventuellement la taille des fichiers a telecharger aussi, dans .htaccess a la racine du site web comme suit:

php_value max_input_time 200
php_value max_execution_time 200
php_value post_max_size 20M
php_value upload_max_filesize 15M