Redirection

#2

redirectpermanent /cssvault http://www.cssvault.com

but that won't keep people's links good.

Maybe something with mod_rewrite?

I know you can do it in PHP by using parseurl() to parse out the address they're trying to reach and rewriting the host variable before using header location for the (permanent) redirect

JC (http://thelionsweb.com/weblog)

#4

Don't move the entire site - just the thumbnails.

Mark Fusco (http://www.lightpierce.com/ltshdw)

#6

Hmm, I remember some http error code that states that a document has been moved; 301 Moved Permanently. But I don't know how the browsers will cope. Will it pick up the url and redirect automaticly, or just show it as an error or maybe even a third option.

So I put up an test page, http://mantaworks.nl/test/error/ . It has an index.php file with two lines:

header("HTTP/1.0 301 Moved Permanently");
header("Location: http://www.php.net/");
?>

Tested in win/firebird 0.7 and win/IE6 and both show the same result: an external redirect. A .htaccess file with a redirect maybe a safer option, but I'm not too happy with tinkering the server. If something goes bad, it goes baaad.

But one fact remains: the user doesn't get any info that the link isn't valid anymore, only a change in the url field of the browser is present. A little check on the new domain for the referer and throwing up some kind of warning would solve that.

[m] (http://mantaworks.nl)

#8

I'm with Mark Fusco on this, only move the images. It's a lot less work and the result would be the same.

Bart N. (http://percept.be)

#10

I would say: "As Mark said, move just the thumbnails. Why not? Simple and fast..."

But what about the the actual mt configuration and entries? Even if mt has a good export/import system with the same effort you'll move the entire CSSVault.

JTG Mark (http://jumpthegap.com/)

#12

Don't over-complicate things - steer clear of PHP redirects. If you're on shared hosting with Apache you really don't want/need the additional overhead. Using PHP will mean that apache still has to process the request, create an instance of PHP, parse and run the PHP script, and then remove the resources used. Thats some overhead when a simple .htaccess file with the lines:
RewriteEngine on
RewriteBase /cssvault
RewriteRule ^/$ http://yournewsite.com/ [R=301,L]

will do everything for you, and with a lot less overhead. Using the R=301 will send a "Moved Permanently" header, so future hits will jump directly to your new host.

Dysfunksional.Monkey (http://dysfunksion.co.uk)

#14

Here's a solution that should work. It would allow you to just move the whole directory structure in its entirety to a new server. Put the following into an .htaccess file in the "/cssvault" directory:

RewriteEngine On

#Rewrite rules
RewriteBase /cssvault # sets the base directory for all following rewrite rules
RewriteRule ^(.*)$ http://www.yournewdomain.com/$1 # Redirects any requests to the new domain, appending any further path information to the path at the new server

Travis Cripps (http://www.apparentmotion.com)

#16

It depends if you want transparent (PHP header() or Apache .htaccess), or nagging (remind people that the location has changed, and to update, using a link page or refresh).

You could also consider emailing webmaster@ advising them of the change in bulk, or automatically once via PHP.

Justin French