Aliasing an URL

Hi there,

Suppose I have this two urls:

http://www.foo.com

and

http://www.bar.com

And suppose that I have access to both of their httpdocs, etc (all
their Apache's internalities),
in their respective servers.

Now, what I intend to do is this:
1. Whenever I paste/click on "www.foo.com" in browser address bar, it
will show all the
"www.bar.com" content in it including all the CGI apps that come with
it.

2. No redirecting page should appear when we paste/click on
"www.foo.com".

3. Whenever the content and CGI apps is accessed/showed for
"www.bar.com",
the address bar should keep showing "www.foo.com".

Thanks and hope to hear from you again.

Regards,
Edward

Re: Aliasing an URL

Scripsit ewijaya:

> Suppose I have this two urls:
>
> http://www.foo.com
>
> and
>
> http://www.bar.com

They are real URLs, but probably not the real URLs you mean. In future,
please post the real URLs _or_ use the pseudo-domain .example to indicate
URLs as fictional.

> Now, what I intend to do is this:
> 1. Whenever I paste/click on "www.foo.com" in browser address bar, it
> will show all the
> "www.bar.com" content in it including all the CGI apps that come with
> it.

What do you mean by that? Why would the main page content include "all the
CGI apps"? It sounds like you would like to have all URLs starting with, eh,
http://www.foo.com
redirected so that "foo" is replaced by "bar" in the server part. On Apache,
which you seem to postulate, that would mean a .htaccess file at the server
root of www.foo.com, containing the line
Redirect permanent / http://www.bar.com/

(If you want temporary redirection only, omit the word permanent.)

> 2. No redirecting page should appear when we paste/click on
> www.foo.com.

There won't be when you do HTTP redirect as above.

> 3. Whenever the content and CGI apps is accessed/showed for
> "www.bar.com",
> the address bar should keep showing www.foo.com.

Why? Why would you show a wrong URL? People who write it down would try to
use it later, and then they would fail to reach your site whenever the
redirecting server www.foo.com is down or disconnected or horribly slow even
though the real server www.bar.com is up and running quite happily.

There are ways to fake the content as coming from an address different from
the real one (frames are the simple trick that people do when they are
ashamed of using some free web space), but let's first see your real
problem.

--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/