From owner-freebsd-stable@FreeBSD.ORG Thu Jul 28 11:37:41 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2468E16A41F for ; Thu, 28 Jul 2005 11:37:41 +0000 (GMT) (envelope-from roger@gwch.net) Received: from mail.gwch.net (80-219-201-207.dclient.hispeed.ch [80.219.201.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DBAF43D58 for ; Thu, 28 Jul 2005 11:37:40 +0000 (GMT) (envelope-from roger@gwch.net) Received: from localhost (link [127.0.0.1]) by mail.gwch.net (Postfix) with ESMTP id A6B8740878 for ; Thu, 28 Jul 2005 13:37:39 +0200 (CEST) Received: from mail.gwch.net ([127.0.0.1]) by localhost (mail.gwch.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02071-02 for ; Thu, 28 Jul 2005 13:37:35 +0200 (CEST) Received: from www.gwch.net (pluto.gwch.net [192.168.2.103]) by mail.gwch.net (Postfix) with ESMTP id B9DF3408A4 for ; Thu, 28 Jul 2005 13:37:35 +0200 (CEST) Received: from 62.2.21.164 (SquirrelMail authenticated user rogerg) by www.gwch.net with HTTP; Thu, 28 Jul 2005 13:37:35 +0200 (CEST) Message-ID: <12605.62.2.21.164.1122550655.squirrel@www.gwch.net> In-Reply-To: <200507281044.j6SAiIIx044768@lurza.secnetix.de> References: <42E8BFBF.1010403@bmby.com> <200507281044.j6SAiIIx044768@lurza.secnetix.de> Date: Thu, 28 Jul 2005 13:37:35 +0200 (CEST) From: "Roger Grosswiler" To: freebsd-stable@FreeBSD.ORG User-Agent: SquirrelMail/1.4.4-2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at gwch.net Cc: Subject: Re: Apache2 just listening to https? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jul 2005 11:37:41 -0000 done. > > You can configure SSL perfectly fine per virtual host, > provided that they have separate addresses. You can > even use SSL for virtual hosts that share an address, > if they listen on different ports (in this case you > can use redirects for convenience, so users don't have > to type the port numbers). > > It's correct that SSL doesn't work for pure name-based > virtual hosts (not using "special tricks"), but nobody > was talking about that. > They are on the same host listening to 80 and 443, i use namedbased version. so, this could be the issue...but i tried with starting without ssl-support and i got the same result. Roger