Customer Support

When using virtual subdomains (where no directory or symlink for the
subdomain in /htdocs exists), there might be some circumstances where
you would want to add a %1 to the end of the last rule:

   RewriteRule ^(.*)$  http://www.yourwebsite.com/%1

That will take a request for a non-existent subdomain such as
"anything":

    http://anything.yourdomain.com

and redirect it to:

    http://www.yourdomain.com/anything

Of course, then you will have to have a file or directory named
"anything" in /htdocs/www/ in order to handle that request properly. If
not, then you should probably change the last rule to:

    RewriteRule ^(.*)$  http://www.yourwebsite.com/script.php?sub=%1

and then have a script at /htdocs/www/script.php that is programmed to
find the GET variable $sub or $_GET["sub"] and perform any actions you
want.

If you don't have your own domain name and are hosting a modwest.com
subdomain to start with (like you.modwest.com) then you should change
the first line of the Rewrite rules to:

    RewriteCond %{HTTP_HOST} ^([a-z0-9]+)\..+\..+\..*$ [NC]

That will make it so that going to http://you.modwest.com will not
invoke any rewriting, while http://something.you.modwest.com will.

Another idea entirely on how to make a catch-all for subdomains that
have not been setup is to use the ErrorDocument directives in an
/htdocs/.htaccess file. You could have 404 errors result in the user
being served a PHP script that has this code:

<?  header("Location: http://www.somesite.com/somepage";); ?>

That way, the PHP script (served as a 404 Not Found page) will send the
browser wherever you want it to go when a subdomain that does not exist
has been requested.