The easiest way to deal with this problem is to not let it happen. A
common method is to force the use of a canonical domain name. In your
case, mysite.com.
If you are using Apache with mod_rewrite, put the following in the
site's .htaccess file:
RewriteEngine On
RewriteCond %{HTTP_HOST} !^mysite\.com [NC]
RewriteRule (.*)$ http://mysite.com/$1 [R=301,L]
This forces any reference to your site that DOES NOT start with
http://mysite.com to get a 301 (Permanent Redirect) to the same page,
but using your canonical domain name.
There is one tiny problem with this, but you are unlikely to encounter
it. If the request is a POST (as opposed to a GET), the the POST data
will be lost on the redirect. This is not a huge problem if you simply
fix their domain name on first contact, which is almost always a GET.
HTH,
Peter
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
