Mega list of redirects (.htaccess)

[RichardGv]

1. Thanks.
2. .htaccess works under both Windows and *nix versions of Apache, as far as the server is configured correctly (depends on AccessFileName and (kind of) AllowOverride).
http://httpd.apache.org/docs/trunk/howto/htaccess.html
(It's nevertheless true that Windows don't hide files with names starting with dot, unlike *nix systems.)
3. There's something that you may want to pay attention, about the directive Redirect:

Redirect Directive
...
Syntax: Redirect [status] URL-path URL
...
Then any request beginning with URL-Path will return a redirect request to the client at the location of the target URL. Additional path information beyond the matched URL-Path will be appended to the target URL...
Source: http://httpd.apache.org/docs/2.2/mod/mod...l#redirect

So, for example, if somebody tries to access http://your-site.com/oldpage.html.old/testpage.html, and you have this rule in your .htaccess:

Code:

Redirect 301 /oldpage.html http://example.com/newpage.html

The result is, the user will be redirected to http://example.com/newpage.html.old/testpage.html. This exception can be troublesome in certain situations.
4. mod_rewrite provides a much more flexible solution that mod_alias for redirections, which you might be interested in:
http://httpd.apache.org/docs/2.2/misc/rewriteguide.html
5. About the example of the removal of .html extension, you can use mod_rewrite to avoid the problem that accesses to existing files are redirected incorrectly:

Code:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^(.*)\.html$ $1.php [L,R=301]

Or you can choice to rewrite the request instead of redirecting it:

Code:

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !=/favicon.ico
RewriteRule ^(.*)\.html$ $1.php [L]

(The code above is not tested. There can be certain issues when using them. The code originally came from Drupal .htaccess.)