moshdj2uk — Sat, 23 Dec 2006 15:26:07 +0000

RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteCond %{HTTP_HOST} ^([^\.]+)\.mydomain\.com$ [NC]
RewriteRule ^(.*)$ somescript.cgi?somevariable=%1 [L]

Try that, obviously replacing the bold values with your own site and page. The above works for me on one of my sites.

There is once thing you will need though: You will need to have a dedicated IP given to you by your host. Ask them and they will give you one at a small cost.

Let me know how you get on.

aci20 — Tue, 19 Dec 2006 18:24:50 +0000

Hi all - I finally had the time and courage to try it, but I have a real annoyance.

mod_rewrite seems to have a problem - it's easy enough to do a rewrite as long as I stay within a certain subdomain, but if I want to refer a script from (for example) http://foo.bar.com/script.cgi to http://bar.com/script.cgi?subdomain=foo, it has to go as a redirect rather than a rewrite; in other words, the new URL appears in the address bar (and I have to write the domain explicitly in the RewriteRule).

Am I stuck with this?

I found something somewhere saying that the [P] tag at the end of the RewriteRule is what I want (proxy???), but it just causes an error (maybe I don't have mod_proxy?)

Hope you can make sense of this gibberish!

aci20 — Sat, 14 Oct 2006 10:04:18 +0000

Thanks guys, I'll read up on mod_rewrite.
Nice to see it's unanimous!

Mark Hensler — Wed, 11 Oct 2006 06:06:15 +0000

Symbolic linking on a *nix platform is also an option.

But mod_rewrite would be the prefered method.

Depending on how your server/config acts, you could opt to not create subdomains (in apache). At this point, all sub-domains should pull up the same site. Then, deploy an .htaccess file in the document_root of your domain, which captures the prefixed subdomain and appends it as part of a querystring.

mr cgi guy — Tue, 10 Oct 2006 20:27:31 +0000

how about mod_rewrite?
you'd need to have an .htaccess file in each directory, but you wouldn't need to duplicate the script then.
would be pretty easy to capture the subdomain value then without having to rely on env variables.

aci20 — Mon, 18 Sep 2006 12:27:33 +0000

Not sure exactly what you're getting at, but I'll try to explain. The subdomains will each appear to be a different, independent site, but there will be one set of scripts. The scripts will be in the server's public_html directory (but made executable via the .htaccess file). My hosting company allows me to set up subdomains, e.g. xyz.mysite.com, but the files for this would normally be placed in a folder 'xyz' (or whatever) which has the same level of hierarchy as public_html. xyz.mysite.com/somescript.cgi would normally try to access the file somescript.cgi within the 'xyz' folder.

I suppose I'm after some command that instructs xyz.mysite.com/somescript.cgi to execute somescript.cgi within public_html, rather than within xyz. I suspect it should be reasonably straightforward for that script to tell which subdomain is accessing it by looking at the environment variables. Of course, I will still want links generated by somescript.cgi to point to xyz.mysite.com/someotherscript.cgi, rather than mysite.com/someotherscript.cgi, otherwise the subdomain information will be lost.

I think I'm confusing myself, as usual. Does that make any kind of sense?

Thanks!

Greg K — Mon, 18 Sep 2006 11:27:51 +0000

Will each subdomain have its own site, or will they all be generated off of the perl scripts based on the subdomain?

If they are only getting the site from the perl scripts, i think I know a way.

-Greg