From owner-freebsd-isp@FreeBSD.ORG  Thu Feb 12 10:03:05 2004
Return-Path: <owner-freebsd-isp@FreeBSD.ORG>
Delivered-To: freebsd-isp@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AEAF316A4CE
	for <freebsd-isp@freebsd.org>; Thu, 12 Feb 2004 10:03:05 -0800 (PST)
Received: from omoikane.mb.skyweb.ca (64-42-246-34.mb.skyweb.ca
	[64.42.246.34])	by mx1.FreeBSD.org (Postfix) with ESMTP id 9A5C643D1F
	for <freebsd-isp@freebsd.org>; Thu, 12 Feb 2004 10:03:05 -0800 (PST)
	(envelope-from mark@skyweb.ca)
Received: by omoikane.mb.skyweb.ca (Postfix, from userid 1001)
	id 83B0162B09; Thu, 12 Feb 2004 12:03:25 -0600 (CST)
Date: Thu, 12 Feb 2004 12:03:25 -0600
From: Mark Johnston <mjohnston@skyweb.ca>
To: "Marc G. Fournier" <scrappy@hub.org>
Message-ID: <20040212180325.GD1278@omoikane.mb.skyweb.ca>
Mail-Followup-To: "Marc G. Fournier" <scrappy@hub.org>,
	freebsd-isp@freebsd.org
References: <2004212181157.302775@juanjo>
	<1076606373.1625.2.camel@p4.unixmexico.net>
	<20040212133729.O96890@ganymede.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040212133729.O96890@ganymede.hub.org>
User-Agent: Mutt/1.4.1i
cc: freebsd-isp@freebsd.org
Subject: Re: Multiple SSL Domains on one IP ...
X-BeenThere: freebsd-isp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Internet Services Providers <freebsd-isp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isp>
List-Post: <mailto:freebsd-isp@freebsd.org>
List-Help: <mailto:freebsd-isp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2004 18:03:05 -0000

"Marc G. Fournier" <scrappy@hub.org> wrote:
> On Thu, 12 Feb 2004, Nicolas de Bari Embriz G. R. wrote:
> 
> > A solution could be to use a different PORT per virtualhost
> >
> > domain1:4430
> > domaim2:4431
> > domain3:4432
> 
> I thought about that ... but there would be no way of doing that
> transparently, would there?  I thought about through the use of the Proxy
> stuff, so you'd have https://domain Proxy for https://domain:4430 ... but
> I don't think that that would flow through, would it?

What about a redirect?  You could run name-based virtual hosting for all
of your domains as http://domain, and have it redirect (rewrite, whatever
you prefer) to https://domain:4430/requestedpath/etc.  As long as the site
uses all relative links, that should work OK - absolute links would knock
the user in and out of SSL mode and screw up form submission.

Mark