lucy24
msg:4378138 | 10:16 pm on Oct 22, 2011 (gmt 0) |
You need to get a firm grip on the difference between mod_alias (what you're using here) and mod_rewrite.
One key difference: Redirects made using mod_alias will reappend the rest of the path. So when you say
Redirect 301 / http://www.example.com/
it really means
Redirect 301 {/blahblah} http://www.example.com{/sameblahblah}
There are times when mod_alias is appropriate* but what you want here is
RewriteEngine On
RewriteRule .* http://www.example.com/ [R=301,L]
* Apache says so. [httpd.apache.org]
|
g1smd
msg:4378141 | 10:24 pm on Oct 22, 2011 (gmt 0) |
SEO wise, it is generally bad form to funnel multiple pages via a redirect to a single target URL, especially so if that target is the root.
Much better would be a one-to-one 301 redirect of old page to equivalent new page.
|
imbckagn
msg:4378146 | 10:36 pm on Oct 22, 2011 (gmt 0) |
Thanks lucy24 but I should have mentioned I tried what you suggested and:
Options +FollowSymLinks
RewriteEngine on
RewriteRule (.*) [newdomain.com...] [R=301,L]
Neither of these options work and both product the same result described in my original post.
g1smd there are no equivalent pages on the new site. I'm killing the whole site and want to funnel all the traffic to the index of the new site.
|
g1smd
msg:4378147 | 10:42 pm on Oct 22, 2011 (gmt 0) |
Use example.com on this forum to stop URL auto-linking.
The RewriteRule code should have worked exactly as you wanted. Is mod_rewrite enabled on that server?
You don't need to pay for two hosting plans. Point both domains at the one server. Install a redirect so that when the request is for the wrong hostname, the server sends a redirect to the correct hostname. When the new request arrives at the same server, but this time for the right hostname, the content is served.
|
|
