g1smd - 1:49 pm on Feb 22, 2010 (gmt 0)

We're going backwards as fast as we're going forwards.

The latest code still has the rewrite before the redirects.

It also has a rule that includes the domain name (so it is a redirect) but no R=301 part, so it produces a 302 redirect.

It's important that YOU learn to spot these errors, so that you can maintain your code on your site.

If it has a domain name and/or an R flag it is a redirect. Perfect code for a redirect has BOTH of those things.

If it has no domain name and no R flag, it is a rewrite.

A redirect maps a URL request to a new URL (forces the browser to request the new URL).

A rewrite maps a URL request to an internal server path (content is served at the requested URL).

Still to do:

- redirect URL requests for .php URLs to new URL.


Correct order:

# Redirect index.php URL request to new / or /folder/ URL.
# Redirect other .php URL requests to new name URL.
# Redirect non-www URL request to www URL.

# Rewrite new name URL request to .php file.


There's better code you can use for the index redirect. Code with .* in the pattern runs very inefficient.


You also need to add the DirectoryIndex index.php statement ahead of all of this stuff.