Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 93826 invoked by uid 500); 22 May 2001 01:02:22 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 93813 invoked from network); 22 May 2001 01:02:20 -0000 Date: Mon, 21 May 2001 18:00:00 -0700 From: "Roy T. Fielding" To: new-httpd@apache.org Subject: Re: Allowing modules to add input filters is broken Message-ID: <20010521180000.I898@waka.ebuilt.net> Mail-Followup-To: "Roy T. Fielding" , new-httpd@apache.org References: <003f01c0e257$bf3cd140$6401a8c0@apache> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.13-current-20010115i In-Reply-To: <003f01c0e257$bf3cd140$6401a8c0@apache>; from bill@wstoddard.com on Mon, May 21, 2001 at 08:39:57PM -0400 X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > I still don't understand what name based virtual hosting has to do with SSL. You can know at global > server scope whether a port/ip pair is SSL or not and you install mod_tls appropriately. Maybe I am > being dense or you are really meaning ip-based host rather than name based (i.e., the Host: header) > virtual hosting. I think Graham is referring to the use of the Upgrade header field to change a connection from HTTP to HTTP-over-SSL, which is described in a recent RFC. That is the only way to use SSL with name-based virtual hosts (as opposed to separate IP address virtual hosts). ....Roy