Hi All,

You don't need to do that at all :)

Use the ErrorDocument (I'm sure thttp has the same thing) to redirect to a
Perl or PHP script.  Just parse out the HTTP ENV variables, get the host
name it was trying to get and redirect.

It's about a 4 line PHP script and I'm sure it's about the same in Perl.

Regards,

Rick

----- Original Message -----
From: "Marc Schneiders" <[EMAIL PROTECTED]>
To: "William X. Walsh" <[EMAIL PROTECTED]>
Cc: "N.B. DelMore" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, October 03, 2000 6:16 AM
Subject: Re: Re[2]: Domain Redirection & Cloaking


On Tue, 3 Oct 2000, William X. Walsh wrote:

> Hello Marc,
>
> Tuesday, October 03, 2000, 2:53:30 AM, you wrote:
>
> > I would be interested to learn, what the advantages of this (or any)
perl
> > script are compared to the simple HTML I posted last night. I am sure
> > there must be something or people wouldn't take all the trouble of
writing
> > perl :-)
>
> Because you would have to setup a virtual server host for each and
> every site you want to redirect.  This consumes huge resources once
> you start to grow.
>
> Our system will use one virtual host for all redirection hosts.  It
> will be dependent on the http1.1 headers for virtual hosting, but the
> number of non-supported users is so minuscule that it is
> insignificant.

Thanks. But this is Apache what you are talking about, right? Sorry, I
should have mentioned I use Thttpd. Not very familiar with Apache. All I
have to do, is add a directory in the htdocs directory: DOMAIN.COM. ln -s
this to www.DOMAIN.COM and change title, keywords, and where to redirect
to in the index.html template. This could all be scripted easily, if it
needs to be done very frequently. But then maybe this is exactly what your
script does? Anyway, not much extra resources used in my set up. Just a
subdirectory and a little file.

--
*---------------------------------------------------------------------*
 Marc Schneiders --- http://bodacious-tatas.org: no not what you think
*---------------------------------------------------------------------*


Reply via email to