Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 356 invoked by uid 500); 6 May 2003 13:25:16 -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 333 invoked from network); 6 May 2003 13:25:15 -0000 Received: from unknown (HELO valkyrie.lmig.com) (143.115.171.151) by daedalus.apache.org with SMTP; 6 May 2003 13:25:15 -0000 Received: from LMP-EXMSG-01.lm.lmig.com (lmp-exmsg-01.lm.lmig.com [147.179.184.90]) by valkyrie.lmig.com (8.11.7+Sun/8.11.6) with ESMTP id h46DPG516753 for ; Tue, 6 May 2003 09:25:16 -0400 (EDT) Received: from LM-EXSITE-01.lm.lmig.com ([147.179.184.84]) by LMP-EXMSG-01.lm.lmig.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 6 May 2003 09:25:15 -0400 Received: from LM-EXMSG-10.lm.lmig.com ([147.179.184.122]) by LM-EXSITE-01.lm.lmig.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 6 May 2003 09:25:15 -0400 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Date: Tue, 6 May 2003 09:25:15 -0400 Message-ID: <8636C212C055EA4E85CC85D2AD62C997027A4D5E@lm-exmsg-10.lm.lmig.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [users@httpd] Redirect question Thread-Index: AcMTznw/7twLoBwpRn2Xe20nBkF3fwAA+JFQ From: "Porter, Mark" To: X-OriginalArrivalTime: 06 May 2003 13:25:15.0343 (UTC) FILETIME=[EDFE45F0:01C313D2] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Subject: RE: [users@httpd] Redirect question We're having the same problem with Cisco load balancers, a Rainbow Igate SSL accelerator, and Iplanet Web Server 4.1. I haven't tried it with Apache, but I suspect the problem will still be there. We had the accelerator vendor write a code update that looks for a redirect containing http instead of https, and the port appended to the host with a :. (we're using port translation, so the web server is actually bound to :84)=20 Remember that if you leave the trailing / off a directory object, the web server actually sends a redirect to the browser, containing the trailing /. The Igate intercepts the redirect, and rewrites it to be https, and (in our case) removes the :84. -----Original Message----- From: P. Dwayne Miller [mailto:dmiller@espgroup.net]=20 Sent: Tuesday, May 06, 2003 9:01 AM To: users@httpd.apache.org Subject: [users@httpd] Redirect question Currently, we have an F5 LoadBalancer with SSL accelerator installed in=20 front of the web server. The F5 is handling requests for=20 https://my.domain.com and the web server sees requests on port 80. If=20 the user sends a request without the trailing slash (i.e.=20 https://my.domain.com/order, where order is a directory), a redirect=20 occurs from the web server, but it seems to redirect the client browser=20 back to http://my.domain.com/order/. This request does not connect as=20 port 80 is blocked at the firewall. The questions is... is this something that I need to set up in the=20 Apache config to cause the redirect to be properly written to https? Or something that the F5 should be handling. Tks, Dwayne --------------------------------------------------------------------- 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