Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 6494 invoked from network); 1 Dec 2009 20:56:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Dec 2009 20:56:47 -0000 Received: (qmail 28666 invoked by uid 500); 1 Dec 2009 20:56:43 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 28609 invoked by uid 500); 1 Dec 2009 20:56:43 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 28600 invoked by uid 99); 1 Dec 2009 20:56:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2009 20:56:43 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mearns.b@gmail.com designates 209.85.218.221 as permitted sender) Received: from [209.85.218.221] (HELO mail-bw0-f221.google.com) (209.85.218.221) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Dec 2009 20:56:40 +0000 Received: by bwz21 with SMTP id 21so3840946bwz.24 for ; Tue, 01 Dec 2009 12:56:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=F9m03xlIcJnhhVx7Ay+JhPmv/jRwR1M4EHKcq1IN9v4=; b=jPEE0VO9u3rIQrURvGhEIXJnP+LfL2ZlmWhnigH+KN3KHbt5BP75mjzHWWkng8Eq25 XIfXBpUkk0xExFWek6Pqv4Fx2H8iiQyxAUrPJWufV8uvA1a8ZBoX7QIw8tTEyUjJJYEc u5TPSGYglKxAe1OqJv8wg3Ibm9szJWYosHQL0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=fsXnOxOoUTMqJjee7Zsh+FSOn7i8mb2ztWKaIENpUa0zAxwC2WuPyvpkZw2T4PxkQO PlLEbaNN9mKtm1SpFcFCDIOGAnnZuicME331c+onPRnwpohAPscaxC9Z3bcIO2A6VC6f OK+ziP6B3sg4zw48Yez4EVBRjIQHk3bQJHAZg= MIME-Version: 1.0 Received: by 10.204.2.131 with SMTP id 3mr6460924bkj.175.1259700979299; Tue, 01 Dec 2009 12:56:19 -0800 (PST) In-Reply-To: <40795.161.203.16.1.1259700539.squirrel@mail.his.com> References: <4B149773.9020109@infoservices.in> <6ed6382b0911302149n353500f2oa3d8a7dca5ebbf8e@mail.gmail.com> <4B14C39B.3080806@infoservices.in> <40795.161.203.16.1.1259700539.squirrel@mail.his.com> From: Brian Mearns Date: Tue, 1 Dec 2009 15:55:59 -0500 Message-ID: <4df3a1330912011255r3ae3d783if985cfca0d6fdab2@mail.gmail.com> To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [users@httpd] how to get multiple SSL with name based vhost ? On Tue, Dec 1, 2009 at 3:48 PM, Sheryl wrote: > >> Krist explained it very nicely... But maybe you still didn't get it: >> Without SNI, there is NO WAY TO DO THIS. It is a fundamental limitation of >> the HTTPS protocol with no production-grade work-around. SNI (server-name >> indication) was specifically added to address this limitation. There is >> simply NO ALTERNATIVE. > > To back up a moment, though -- another way to do this is to define > multiple IPs on the network card and run multiple instances of apache, > each with different config files. [snip] That's only if he has multiple IP addresses available on the network, right? If we assume this is a public sever, that means he needs multiple public IP addresses from his ISP that route to this server. That's certainly a possibility, in general, but I want to make sure I'm not missing something awesome. -Brian -- Feel free to contact me using PGP Encryption: Key Id: 0x3AA70848 Available from: http://keys.gnupg.net --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org