From owner-freebsd-isp  Mon Jun  9 10:30:33 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA03618
          for isp-outgoing; Mon, 9 Jun 1997 10:30:33 -0700 (PDT)
Received: from uhf.wdc.net (uhf.4d.net [207.137.157.140])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA03609
          for <freebsd-isp@FreeBSD.ORG>; Mon, 9 Jun 1997 10:30:27 -0700 (PDT)
Received: from localhost (bad@localhost) by uhf.wdc.net (8.8.5/8.6.12) with SMTP id NAA01279; Mon, 9 Jun 1997 13:31:12 -0400 (EDT)
Date: Mon, 9 Jun 1997 13:31:08 -0400 (EDT)
From: Bernie Doehner <bad@uhf.wireless.net>
To: Josef Karthauser <joe@pavilion.net>
cc: freebsd-isp@FreeBSD.ORG
Subject: Re: Waiting for reply...
In-Reply-To: <19970609165934.44723@pavilion.net>
Message-ID: <Pine.BSF.3.95.970609132859.1139G-100000@uhf.wdc.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > 1. Upgrade apache to 1.2
> 
> Is this a concern?  I'm running 1.1.3 on a production machine and am
> about to upgrade it to 1.2.  Is this going to be straight-forward, or
> am I going to have to take anything into account?

Not sure. 1.1.3 is so old, I don't even remmember when I first ran a 1.2
beta. Still uses same Configuration/make procedure, but I am sure there
are new modules. You'll probably have to edit the new Configuration file
ot your liking.

Regarding the .conf files, I don't think anything changed.

Oh yea.. proxying works a lot better in 1.2.

Bernie