hi tbeasley123,
On the ExtraNet server, you could use apache ProxyPass/ProxyPassReverse
So let say you had this setup.
intranet.domain.com - 192.168.0.100
extranet.domain.com - 123.123.123.123
You apache config (Extranet)
<VirtualHost *:80>
# This is for the ExtraNet stuff.
ServerName www.domain.com
ServerAlias extranet extranet.domain.com domain.com
#
# rest of config goes here
#
</VirtualHost>
<VirtualHost *:80>
# This is for the Intranet proxy
ServerName intranet.domain.com
ServerAlias intranet
ProxyPass / http://192.168.0.100/
ProxyPassReverse / http://192.168.0.100/
</VirtualHost>
If you need to maintain the name intranet in the content (on Extranet server), you would need to publish the intranet.domain.com on the public DNS -- so that it would be 123.123.123.123.
With this setup, request to http://intranet/docs/somet
IntraNet server. Request from public, would hit the Extranet server, but it would be proxied (silently) to http://192.168.0.100/docs/
I had some detailed writeup on the following PAQ.
http://www.experts-exchang
Main Topics
Browse All Topics
by: dharmanerdPosted on 2007-08-29 at 15:49:02ID: 19796049
I'd use a sym link. this will require your permissions to be set correctly.
from a command prompt
ln -s external/files internal/files/public_site
now let's assume your document root is internal/files you can access like so...
http://internal_ip_or_doma
For this to work well, you php from the public site should probably be using absolute references to things like images, css, etc.
now if you say were writing a new php script for the internal site, but wanted to use the database library from the public site, you can do something like this (provide permissions are set correctly)
<?php
//new internal php script
include "/external/files/functions