The redirection<\/a> of www.yourdomain.ext\/default.html<\/strong> or <\/em>index.html to http:\/\/www.yourdomain.ext\/index.php?act=whatever<\/strong> redirects it to http:\/\/www.yourdomain.ext\/index.php%3fact=whatever<\/strong>. In other words, why is “?” replaced with “%3f” (or anything else) in the address line? Why is your php redirect not working?<\/p>\n\n\n\n The solution below will show how to fix PHP redirect issues using Apache’s mod_rewrite module<\/a>. The mod_rewrite module is a tool that allows you to manipulate URLs using an unlimited number of rules. You can attach an unlimited number of rule conditions to each rule. This allows you to rewrite URLs by considering server variables, HTTP headers, environment variables, or time stamps.<\/p>\n\n\n\n To fix the php redirect problem, you can use the mod_rewrite module<\/a> to redirect a URL to another URL, transform long URLs into short ones, redirect missing pages, and more.<\/p>\n\n\n\n Begin rewriting:<\/p>\n\n\n\n Whenever you use mod_rewrite, you need only to do this once per .htaccess file<\/a>:<\/p>\n\n\n\n Before any ReWrite rules, +FollowSymLinks<\/strong> must be enabled for any rules to work. This is a security requirement of the rewrite engine. Usually, it is enabled in the root, and you should not have to add it.<\/p>\n\n\n\n The following line switches on the rewrite engine for that folder. If this directive is in your main .htaccess file, then the ReWrite engine is theoretically enabled for your entire site. It is wise always to add that line before you write any redirections. While some of the directives on this page may appear split into two lines, in your .htaccess file, they must exist entirely on one line.<\/p>\n\n\n\n Note:<\/strong> For instructions on how to do a PHP header redirect and best practices for using php header redirects, check out the article: How to Code a PHP Redirect – PHP Header Redirect<\/a>.<\/p>\n\n\n\n Apache scans all incoming URL requests, checks for matches in your .htaccess file, and rewrites those matching URLs to whatever you specify. For example:<\/p>\n\n\n\n This can be helpful for anyone updating a site from static HTML (you could use .html or .htm(.*)) to dynamic PHP pages, where requests to the old pages are automatically rewritten to your new URLs. Visitors and search engines can access your content either way. Moreover, this enables you to split PHP code and its included HTML structures into two separate files, making editing and updating easy. The [nc] part at the end means “No Case” or “case-insensitive”.<\/p>\n\n\n\n Users can link to whatever.html<\/strong> or whatever.php<\/strong>, but they always get whatever.php<\/strong> <\/em>in their browser, which works even if whatever.html<\/strong> doesn’t exist.<\/p>\n\n\n\n It can be tricky. Visitors will still have whatever.html<\/strong> in their browser address bar and will still keep bookmarking your old .html URLs. This is a php redirect loop. Search engines will also keep on indexing your links as .htm<\/strong>. Some have even argued that serving up the same content from two different places could have you penalized by search engines. This may or may not bother you, but if it does, mod_rewrite can help:<\/p>\n\n\n\n This time, we instruct mod_rewrite to send a proper HTTP (permanently moved) redirection, also known as a 301 redirect. The user’s browser is physically redirected to a new URL, and whatever.php<\/strong> appears in their browser’s address bar, search engines and other entities will automatically update their links to the .php versions.<\/p>\n\n\n\n You may have noticed that the above examples use a regular expression to match variables. That means it matches the part inside (.+) and uses it to construct “$1” in the new URL. In other words, (.+) = $1, you could have multiple (.+) parts, and for each, mod_rewrite automatically creates a matching $1, $2, $3, etc., in your target URL. For example:<\/p>\n\n\n\n This would allow you to present a link as:<\/p>\n\n\n\n and in the background, have that translated to:<\/p>\n\n\n\n which some scripts could process. Many search engines simply do not follow our ?generated=links<\/em>. So, if you create generating pages, this is useful. Google will handle a good few parameters in your URL without any problems. However, other search engines will not.<\/p>\n\n\n\n Presenting links as\/standard\/paths means you’re less likely to get users making typos in typed URLs.<\/p>\n\n\n\n Using the code above would enable anyone to access blog archives by doing:<\/p>\n\n\n\n in their browser and have it automatically transformed server-side into:<\/p>\n\n\n\n which yourdomainblog would understand. It’s easy to see that you can perform some URL manipulations with a basic understanding of POSIX regular expression.<\/p>\n\n\n\n One common use of mod_rewrite is to shorten URLs. Shorter URLs are easier to remember and easier to type. For example:<\/p>\n\n\n\n This rule would transform the user’s URL server-side:<\/p>\n\n\n\n into:<\/p>\n\n\n\n With this technique, you can move \/public\/files\/download\/ to anywhere else on your site, and all the old links still work fine. Just change your .htaccess file to reflect the new location. Edit one line, and you are done.<\/p>\n\n\n\n You may see the last line broken into two, but it’s all one line (all the directives on this page are). So, take a look at what it does.<\/p>\n\n\n\n We begin by enabling the rewrite engine, as always.<\/p>\n\n\n\n The first RewriteCond line allows direct requests (not from other pages – an “empty referrer”) to pass unmolested. The next line means if the browser did send a referrer header and the word “yourdomain” is not in the domain part of it, then DO rewrite this request.<\/p>\n\n\n\n The final RewriteRule line instructs mod_rewrite to rewrite all matched requests (anything without “yourdomain” in its referrer), asking for gifs, jpegs, or pngs to an alternative image.<\/p>\n\n\n\n Remember, if you put these rules in the main server conf file (usually httpd.conf) rather than a .htaccess file, you’ll need to use ^\/… .<\/strong>..<\/strong> instead of ^… … <\/strong>at the beginning of the RewriteRule line, in other words, add a slash. But since httpd.conf is restricted to access, this does not apply at Bluehost.<\/p>\n\n\n\n If you are creating rules in the subfolders of your site, please read below.<\/p>\n\n\n\n Note that rules in top folders apply to all the folders inside those folders. We call this “inheritance.” Usually, this works. However, if you start creating other rules inside subfolders, you will obliterate the rules already applying to that folder due to inheritance or descendency if you prefer just the ones applying to that subfolder. For example:<\/p>\n\n\n\n Let’s say you have a rule in your main \/.htaccess that redirects requests for files ending .html <\/strong>to their .php <\/strong>equivalent, just like the example earlier. Now, if you need to add some rewrite rules to your \/osx\/.htaccess file, the .html <\/strong>>> .php<\/strong> redirection will no longer work for the \/osx\/ subfolder. You must reinsert it but with a crucial difference.<\/p>\n\n\n\n Below is the updated \/osx\/. htaccess file, with the .html<\/strong> >> .php<\/strong> redirection rule reinserted, but you will need to reinsert the rules for it to work in this subfolder:<\/p>\n\n\n\n Spot the difference in the subfolder rule. You must add the current path to the new rule. Now it works again. If you remember this, you can go replicating rewrite rules all everywhere.<\/p>\n\n\n\n Mod_rewrite allows you to send browsers from anywhere to anywhere. Moreover, you can create rules on the requested URL and on the IP address, browser agent (send old browsers to different pages, for instance), and even the time of day.<\/p>\n\n\n\nSolution<\/h2>\n\n\n\n
# time to get dynamic, see..\nrewriterule ^(.*).html $1.php<\/code><\/pre>\n\n\n\nOptions +SymlinksIfOwnerMatches\nRewriteEngine on<\/code><\/pre>\n\n\n\n<\/a>Simple Rewriting<\/h3>\n\n\n\n
#all requests to whatever.html will be sent to whatever.php:\nOptions +SymlinksIfOwnerMatches\nRewriteEngine on\nRewriteRule ^(.*).html $1.php [nc]<\/code><\/pre>\n\n\n\n# this will do a \"real\" http redirection:\nOptions +SymlinksIfOwnerMatches\nrewriteengine on\nrewriterule ^(.+).htm$ http:\/\/yourdomain.ext\/$1.php [r=301,nc]<\/code><\/pre>\n\n\n\n<\/a>Complex Rewriting<\/h3>\n\n\n\n
# a more complex rewrite rule:\nOptions +SymlinksIfOwnerMatches\nRewriteEngine on\nRewriteRule ^files\/(.+)\/(.+).zip download.php?section=$1&file=$2 [nc]<\/code><\/pre>\n\n\n\nhttp://mysite\/files\/games\/hoopy.zip<\/code><\/pre>\n\n\n\nhttp://mysite\/download.php?section=games&file=hoopy<\/code><\/pre>\n\n\n\n#an even more complex rewrite rule:\nOptions +SymlinksIfOwnerMatches\nRewriteEngine on\nRewriteRule ^blog\/([0-9]+)-([a-z]+) http:\/\/yourdomain.ext\/blog\/index.php?archive=$1-$2 [nc]<\/code><\/pre>\n\n\n\nhttp://yourdomain.ext\/blog\/2003-nov<\/code><\/pre>\n\n\n\nhttp://yourdomain.ext\/blog\/index.php?archive=2003-nov<\/code><\/pre>\n\n\n\n<\/a>Shorten URLs<\/h3>\n\n\n\n
# beware the regular expression:\nOptions +SymlinksIfOwnerMatches\nRewriteEngine On\nRewriteRule ^grab(.*) \/public\/files\/download\/download.php$1<\/code><\/pre>\n\n\n\nhttp://mysite\/grab?file=my.zip<\/code><\/pre>\n\n\n\nhttp://mysite\/public\/files\/download\/download.php?file=my.zip<\/code><\/pre>\n\n\n\nhttp:\/\/yourdomain.ext\/img\/hotlink.png [nc]<\/code><\/pre>\n\n\n\n<\/a>httpd.conf<\/h3>\n\n\n\n
<\/a>Inheritance<\/h3>\n\n\n\n
# this works fine, site-wide, in my main .htaccess file\n# main (top-level) .htaccess file..\n# requests to file.html goto file.php\nOptions +SymlinksIfOwnerMatches\nrewriteengine on\nrewriterule ^(.*).htm$ http:\/\/yourdomain.ext\/$1.php [r=301,nc]<\/code><\/pre>\n\n\n\n# \/osx\/.htaccess file..\nOptions +SymlinksIfOwnerMatches\nrewriteengine on\nrewriterule some rule that I need here\nrewriterule some other rule I need here\nrewriterule ^(.*).htm$ http:\/\/yourdomain.ext\/osx\/$1.php [r=301,nc]<\/code><\/pre>\n\n\n\n<\/a>Summary<\/h2>\n\n\n\n