Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 83701 invoked by uid 500); 5 May 2003 12:57:28 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 83484 invoked from network); 5 May 2003 12:57:26 -0000 Message-ID: <3EB65FB4.5050205@us.ibm.com> Date: Mon, 05 May 2003 08:57:24 -0400 From: Allan Edwards User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: ProxyPass /foo https://foo.web.site References: <3EB2AB08.9050907@nasa.gov> <3EB2E76C.8050905@us.ibm.com> <3EB2E9BA.9070500@nasa.gov> In-Reply-To: <3EB2E9BA.9070500@nasa.gov> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Chris Knight wrote: > Correct me if I'm wrong, but I believe this only works if the Apache > server is running HTTPS on the front side...I would like to speak HTTP > to the client and HTTPS to the server. No, it lets you talk SSL on the backend. You don't need this directive to talk SSL on the front end (with non SSL on the backend). Allan