0

I have this code that redirects all .php to no extension: 

RewriteCond %{REQUEST_FILENAME} !-d 
RewriteCond %{REQUEST_FILENAME}\.php -f 
RewriteRule ^(.*)/$ $1.php

So /example.php = /example

I would like it so if someone clicks on /example.php that they would automatically end up at /example instead.

What would be the best way to go about it? Would having both links work be considered duplicate content?

checkenginelight
  • 1,116
  • 8
  • 20

2 Answers2

2

Try this one:

RewriteEngine On

# if requested .php file directly, then redirect to extension-less URL
# (do it on initial rewrite iteration only)
RewriteCond %{ENV:REDIRECT_STATUS} ^$
RewriteRule ^(.+)\.php$ /$1 [R=301,L]

# Your "add .php file extension" rule goes below

The problem with this approach is that %{ENV:REDIRECT_STATUS} variable may not be populated/supported by your Apache setup/configuration. Unfortunately I do not know what needs to be done to have it working.

If the above does not work, try this workaround -- it will work but not that "nice" and may fail under some circumstances (query string value is the weak point here):

RewriteEngine On

# if requested .php file directly, then redirect to extension-less URL
# (do it on initial rewrite iteration only)
RewriteCond %{THE_REQUEST} ^[A-Z]+\s.+\.php\sHTTP/.+
RewriteRule ^(.+)\.php$ /$1 [R=301,L]

# Your "add .php file extension" rule goes below

Rewrite condition in this rule is important -- without it you will have endless redirect loop, which your browser will abort at some point (unless it is not smart enough (or request is done by some poorly coded bot) and such process has to be killed manually).

It does not really matter if you place such redirect rule above or below your "add .php file extension" rule -- I just prefer keeping all 301 Redirects close to the top.

LazyOne
  • 158,824
  • 45
  • 388
  • 391
0

You can do a 301 "moved permanently" redirection, which informs the client that the requested resource has moved and is available at a new location. To do that using RewriteRule, add a [R=301,L] flag to the rule specification, e.g.:

RewriteRule ^(.*)/$ $1.php [R=301,L]

This is considered the "search engine friendly" redirection method.

Michał Wojciechowski
  • 2,480
  • 15
  • 9
  • When I add this to my code I can visit my /example.php page but not the /example page as it redirects to somethign like this: http://www.domain1.com/home/username/domains/domain1.com/public_html/example.php I want it when I try to click /example.php it'll automatically take me to /example – checkenginelight Sep 11 '11 at 22:40
  • Then you need to write the rule the other way around: `RewriteRule (.*).php$ /$1 [R=301,L]` – Michał Wojciechowski Sep 11 '11 at 23:17