List,
It seems to me that there are more ways to configure Apache than there are
people willing to do it. It has to be one of the most configurable
packages there is. I see a couple of options here
1) Configure your DNS so it has an alias for your AW, then configure Apache
so that any requests coming to that alias get handled from a different
directory tree. One directory tree is your stuff, the other is the Foxboro
remote access stuff. Then tell whichever group you want (either Foxboro or
your regular users) which name to use.
See the documentation at http://httpd.apache.org/docs/vhosts/name-based.html
2) Configure Apache for IP-based virtual hosting. This requires two
ethernet cards (in addition to the nodebus) and some help from your IT
people. Tell foxboro to use the address (or name) of one card, and your
internal people can have access through the other card. See the
documentation at http://httpd.apache.org/docs/vhosts/ip-based.html
In any case, there is surely a work-around to what should not be a problem
in the first place.
Winston Jenks
Technical Director, Cape Software, Inc.
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
