Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 89388 invoked from network); 6 Jan 2004 21:09:07 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Jan 2004 21:09:07 -0000 Received: (qmail 1219 invoked by uid 500); 6 Jan 2004 21:08:35 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 1189 invoked by uid 500); 6 Jan 2004 21:08:35 -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: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 1176 invoked from network); 6 Jan 2004 21:08:35 -0000 Received: from unknown (HELO out1.smtp.messagingengine.com) (66.111.4.25) by daedalus.apache.org with SMTP; 6 Jan 2004 21:08:35 -0000 X-Sasl-enc: 51BJIUo7bjyeNci9w+5Uxg 1073423293 Received: from usager55-41.hec.ca (usager55-41.hec.ca [132.211.55.41]) by mail.messagingengine.com (Postfix) with ESMTP id 5A5F64A02B3 for ; Tue, 6 Jan 2004 16:08:13 -0500 (EST) Date: Tue, 6 Jan 2004 16:03:55 -0500 (Est) From: Joshua Slive To: users@httpd.apache.org In-Reply-To: <20040106185105.11086.qmail@web20512.mail.yahoo.com> Message-ID: References: <20040106185105.11086.qmail@web20512.mail.yahoo.com> X-X-Sender: slive@fastmail.fm@mail.messagingengine.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: Re: [users@httpd] Reverse Proxy HTTP and HTTPS without VHosts X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Tue, 6 Jan 2004, James Hurne wrote: > So, what I want is to have Apache listen for both HTTP > and HTTPS connections, and handle the HTTPS > connections for our web applications, and the > non-HTTPS connections for Sametime to allow it to > tunnel over HTTP on port 443. No, I don't believe that is possible. Each port/IP combination must be dedicated either to HTTP or HTTPS, since the connections for the two types of protocols are setup in very different ways. This is not a problem specific to apache. You could host one server on 443 and one on 442, but you may still end up with problems with firewalls. It sounds to me like you need to talk to the firewall maintainers either at your site or at your clients' sites. Joshua. --------------------------------------------------------------------- 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