From owner-freebsd-questions  Wed Feb 19 19:01:09 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA09486
          for questions-outgoing; Wed, 19 Feb 1997 19:01:09 -0800 (PST)
Received: from d2si.com (cs2-10.protocom.com [204.72.128.210])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09481
          for <freebsd-questions@FreeBSD.ORG>; Wed, 19 Feb 1997 19:01:04 -0800 (PST)
Received: (from alec@localhost) by d2si.com (8.8.3/8.8.3) id VAA08095; Wed, 19 Feb 1997 21:00:44 -0600 (CST)
From: Alec Kloss <alec@d2si.com>
Message-Id: <199702200300.VAA08095@d2si.com>
Subject: Re: Moving my web
To: vam@recruiter.on.ca (Vic Metcalfe)
Date: Wed, 19 Feb 1997 21:00:43 -0600 (CST)
Cc: freebsd-questions@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.970219155243.15139A-100000@recruiter.on.ca> from Vic Metcalfe at "Feb 19, 97 04:00:06 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Vic Metcalfe is responsible for:
> Hi,
> 
> I am running FreeBSD 2.1.0 as our primary Internet gateway.  Most of the 
> other machines on the lan are Win95/NT plus one Linux box.  I am running 
> our web site with Apache on the FreeBSD box.  I would like to move it to 
> AOLServer though, which doesn't work with FreeBSD.  It uses the close() 
  ^^^^^^^^^What is this?          FreeBSD most certainly has this ^^^^^^^
> call which I don't believe is supported under FreeBSD.  Many users access 
> our web page with http://recruiter.on.ca instead of 
> http://www.recruiter.on.ca, so I can't simply update the DNS to make the 
> change.
> 
> I thought it might be possible to have recruiter.on.ca (FreeBSD) route 
> all traffic to port 80 through to mirromir.recruiter.on.ca (Linux).  Am I 
> dreaming, or are such things possible?
> 
> Thanks in advance,
>   Vic.
> 
Such things are possible although I'd try to discourage your
users from using http://recruiter.on.ca because of exactly
the problem you are now facing.  I'm not quite sure how to
discourage them, but installing a packet forwarder of any
sort certainly won't get them to stop using http://recruiter.on.ca 
instead of http://www.recruiter.on.ca.  I'd recommend
keeping Apache on recruiter and using a redirect in a conf.
file or .htaccess file to redirect http clients away from
recruiter.  Most clients don't even notify the user when
this happens--they just change the URL and try again.  I'll
send you a .htaccess file I use to do this.