I’ll check out the www/non-www idea, but I thought I should post the actual error I received:
Redirecting to http://www.poweredbyearthgirl.com/~happyday/ will cause a redirection loop because 'http://happydayprints.com/'
which is located at /home/happyday/public_html/
is above 'http://www.poweredbyearthgirl.com/~happyday/'
which is located at /home/happyday/public_html/~happyday/
Patience, Prudence! With the speed with which DNS updated propagate, it’s likely that your “problem” has already been resolved - assuming that you’ve updated the domain’s pointers at the registrar.
FWIW, you’ve hit on the better solution, though, which mod_alias’s Redirect can easily handle: Redirect 302 / http://123.456.78.90/~example/ at the old server. Obviously, do NOT use that on the new server!
Dan,
This looks like a DNS propagation delay so both example.com and www.example.com would point to either the old or new server, they would not point to both. Good thought, though.
Yes, we’re all used to the SPEED of the Internet yet forget to allow hosts to update their DNS databases. While it (seemingly) NEVER takes the full three days they advise, it’s rarely immediate (and 6-12 hours is a good range to look for propagation). It’s a common problem and easy to recognize if you’ve seen it before.