asked on

Apache Redirect

I have xyz.com (example url) registered and serving pages to the internet.
The Setup is the following:

Server: Apache-AdvancedExtranetServer/2.0.47 (Mandrake Linux/6.3.92mdk) mod_perl/1.99_09 Perl/v5.8.1 mod_ssl/2.0.47 OpenSSL/0.9.7b PHP/4.3.2

Server 2 has: Apache 1.3.33 Win32/

For corporate reasons, my boss wants to add a secured portion to the website, but on a total different server. This web server does not have a .com registered.

Basically, I want to add a hyperlink on the xyz.com site that points to the other web server, then from there on, they are on server 2.
So, am I able to reroute traffic from xyz.com to Server 2 without server 2 having a registered .com?

ASKER CERTIFIED SOLUTION

yuzh

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

wesly_chen

> This web server does not have a .com registered.
> Redirect /securedir https://server2

Hi yuzh,

I wonder you need to use IP instead of FQDN in httpd.conf. Otherwise, the reader won't be able to
got that URL since the server2 is not registered (no FQDN).

Regards,

Wesly

yuzh

if server2 has internel DNS record, or defined in NIS, or LDAP or files (/etc/hosts), you can use hostname, otherwise, have to use server2's IP.

SOLUTION

wesly_chen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

colonytire

Your visitors from the WAN side will need an IP at minimum to be sent back to the browser. Secondly you will need a second IP. If available, use any form of redirect. I use the html redirect above most of the time
<meta http-equiv="refresh" content="0;URL=http://69.256.34.254"> where 69.256.34.254 is your second available IP.

Now, if you don't have a second ip available, then it can actually get easier, lol. Using prort forward rules, set port 81 to point to server2 on your LAN. Now in your redirect you can use your FQDN and a port switch to get to your other server. It would look like this
<meta http-equiv="refresh" content="0;URL=http://www.domainname.com:81">
make note the port switch [ :81 ] added after the extension

Hope this helps.