From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1M1fvP-0006X4-QU for garchives@archives.gentoo.org; Wed, 06 May 2009 12:08:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 08C27E0359; Wed, 6 May 2009 12:08:34 +0000 (UTC) Received: from mtaout02-winn.ispmail.ntl.com (mtaout02-winn.ispmail.ntl.com [81.103.221.48]) by pigeon.gentoo.org (Postfix) with ESMTP id 977C9E0359 for ; Wed, 6 May 2009 12:08:33 +0000 (UTC) Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090506120829.ZZLX4080.mtaout02-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com> for ; Wed, 6 May 2009 13:08:29 +0100 Received: from sol.anferny.me.uk ([82.3.168.124]) by aamtaout03-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090506120828.LCQQ2093.aamtaout03-winn.ispmail.ntl.com@sol.anferny.me.uk> for ; Wed, 6 May 2009 13:08:28 +0100 Received: from localhost (unknown [127.0.0.1]) by sol.anferny.me.uk (Postfix) with ESMTP id CB9DE2946DC for ; Wed, 6 May 2009 12:08:26 +0000 (UTC) X-Virus-Scanned: amavisd-new at anferny.me.uk Received: from sol.anferny.me.uk ([127.0.0.1]) by localhost (anferny.me.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gm7VVGZS0Fb3 for ; Wed, 6 May 2009 13:08:18 +0100 (BST) Received: from [192.168.16.16] (host213-123-226-159.in-addr.btopenworld.com [213.123.226.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sol.anferny.me.uk (Postfix) with ESMTPSA id B7B081DBC7B for ; Wed, 6 May 2009 13:08:18 +0100 (BST) Message-ID: <4A017DA0.7010802@anferny.me.uk> Date: Wed, 06 May 2009 13:08:00 +0100 From: Anthony Metcalf User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] A networking question... References: <4A00A266.9070102@shic.co.uk> <200905052324.07892.saschahlusiak@arcor.de> <4A00AF76.9010509@shic.co.uk> <20090506062408.7b03652d@coercion> <20090506085459.5e0418c5@krikkit.digimed.co.uk> <4A0161EE.7090308@anferny.me.uk> <20090506114203.7cb2ecf8@krikkit.digimed.co.uk> In-Reply-To: <20090506114203.7cb2ecf8@krikkit.digimed.co.uk> Content-Type: multipart/alternative; boundary="------------020008080606010900000208" X-Cloudmark-Analysis: v=1.0 c=1 a=X8e1wCDZGtYA:10 a=jLiizsvQ4TEA:10 a=uqOi0FLFWo5cdtCcrScA:9 a=AAmE-DE9ERYD5qy6dbizayVM1RUA:4 a=ptTZT96OAAAA:8 a=rm3We1Pf5YWwvwGhqRSmkbW_fDYA:4 X-Archives-Salt: 2a96c4da-324b-443a-8850-3d3d3fb313d3 X-Archives-Hash: 32538aba192001df60d0bc658525e52a This is a multi-part message in MIME format. --------------020008080606010900000208 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Neil Bothwick wrote: > On Wed, 06 May 2009 11:09:50 +0100, Anthony Metcalf wrote: > > >>> If the second server is only serving HTTPS, you don't even need that. >>> Just have the router forward port 80 to the first server and port 443 >>> to the second. >>> >>> >> That leaves the HTTPS server open to the public though, which is >> specifically not allowed to the OP. >> > > He can use HTTP authentication to prevent that. > *That* depends on the exact specifics of what he is/isn't allowed to be showing....."They" may not even want the service to show as existing at that address for whatever reason. --------------020008080606010900000208 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Neil Bothwick wrote: 
On Wed, 06 May 2009 11:09:50 +0100, Anthony Metcalf wrote:

  
If the second server is only serving HTTPS, you don't even need that.
Just have the router forward port 80 to the first server and port 443
to the second.
    
      
That leaves the HTTPS server open to the public though, which is
specifically not allowed to the OP.
    

He can use HTTP authentication to prevent that.
*That* depends on the exact specifics of what he is/isn't allowed to be showing....."They" may not even want the service to show as existing at that address for whatever reason.
--------------020008080606010900000208--