Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 29268 invoked by uid 6000); 17 Jun 1999 20:44:46 -0000 Received: (qmail 29201 invoked from network); 17 Jun 1999 20:44:36 -0000 Received: from imelda.pcug.co.uk (@194.153.26.61) by taz.hyperreal.org with SMTP; 17 Jun 1999 20:44:36 -0000 Received: (qmail 1049 invoked from network); 17 Jun 1999 20:44:26 -0000 Received: from uk2.imdb.com (195.224.85.202) by imelda.pcug.co.uk with SMTP; 17 Jun 1999 20:44:26 -0000 Date: Thu, 17 Jun 1999 21:43:40 +0100 (BST) From: Rob Hartill To: new-httpd@apache.org Subject: Re: trailing '/' redirects from requested port to port 80 ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Thu, 17 Jun 1999, Marc Slemko wrote: > On Thu, 17 Jun 1999, Rob Hartill wrote: > > > > > I'm back... for a minute :-) > > > > Is there a config option to tell Apache to perform trailing '/' redirects > > on port 80 even though requests are coming in on another port ?. > > Just use the Port directive. > > Use a Listen directive to tell Apache what port to listen on, and a Port > directive to tell it what port to think it is listening on. I was doing that and it didn't work. I have virtual hosts that have to be told that their requests come in on port 4000 and they then trigger Apache to send out the redirects with with :4000 tagged on. That method works without virtual hosts, but no combination of configs I tried would let me have working vhosts and working '/'-redirects. -- Rob Hartill Internet Movie Database (www.moviedatabase.com). An Amazon.com company.