Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 15787 invoked from network); 23 Jun 2005 23:57:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Jun 2005 23:57:46 -0000 Received: (qmail 18189 invoked by uid 500); 23 Jun 2005 23:57:36 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 18178 invoked by uid 500); 23 Jun 2005 23:57:36 -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 18159 invoked by uid 99); 23 Jun 2005 23:57:36 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2005 16:57:36 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [205.227.150.16] (HELO ussm001a.mmsa.com) (205.227.150.16) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jun 2005 16:57:36 -0700 In-Reply-To: <200506231538.j5NFcBhj030176@mail.benxcel.com> To: users@httpd.apache.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004 Message-ID: From: Jignesh Badani Date: Thu, 23 Jun 2005 16:56:03 -0700 X-MIMETrack: Serialize by Router on USSM001A/M/MMCX(Release 6.5.4|March 27, 2005) at 06/23/2005 04:57:12 PM, Serialize complete at 06/23/2005 04:57:12 PM Content-Type: text/plain; charset="US-ASCII" X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] https redirect X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Shawn, this does not make sense. In the new server design you want: ServerOld (https) ---- IP Address 1 ---- https://www.domain.com ServerNew (http) ---- IP Address 2 ---- http://www.domain.com So inorder for this to work, you will need to implement some kind of Route decision to route https://www.domain.com request to IP 1 and http://www.domain.com to IP 2. If this is possible and you have it working, then why/how will the secure traffic come to the unsecure server (ServerNew) in the first place and vice-versa !? Excuse me if I am missing something !? "Shawn Marchewka" 06/23/2005 08:42 AM Please respond to users@httpd.apache.org To cc Subject [users@httpd] https redirect I have a site. We'll say it's http://www.domain.com . On the same server, I have https://www.domain.com . Each site has different content. The none secure site is more of a "marketing" side of the server, while the secure site, is a site for customer login, etc. We now see the need to move the non-secure site to it's own server. So I need apache to redirect all the non-secure traffic from the old server to the new server, and all the secure traffic from the new server to the old server. I have accomplished the non-secure traffic of the old server to be redirected, but I can't get the new server secure traffic to be redirected. is this even possible? -Shawn Shawn Marchewka --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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