Return-Path: Delivered-To: apmail-httpd-bugs-archive@www.apache.org Received: (qmail 45713 invoked from network); 1 Apr 2004 23:20:58 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 1 Apr 2004 23:20:58 -0000 Received: (qmail 79176 invoked by uid 500); 1 Apr 2004 23:20:43 -0000 Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org Received: (qmail 79141 invoked by uid 500); 1 Apr 2004 23:20:43 -0000 Mailing-List: contact bugs-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Apache HTTPD Bugs Notification List" Delivered-To: mailing list bugs@httpd.apache.org Received: (qmail 79126 invoked from network); 1 Apr 2004 23:20:43 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 1 Apr 2004 23:20:43 -0000 Received: (qmail 4835 invoked by uid 50); 1 Apr 2004 23:21:29 -0000 Date: 1 Apr 2004 23:21:29 -0000 Message-ID: <20040401232129.4834.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: bugs@httpd.apache.org Cc: Subject: DO NOT REPLY [Bug 28144] New: - mozilla seems to stumble on a https 1.1 site with multiple redirects X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28144 mozilla seems to stumble on a https 1.1 site with multiple redirects Summary: mozilla seems to stumble on a https 1.1 site with multiple redirects Product: Apache httpd-2.0 Version: 2.0.49 Platform: Other URL: http://gamma.fortn.net/basen OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: mod_proxy AssignedTo: bugs@httpd.apache.org ReportedBy: kajtzu@basen.net Note: I'm filing this against httpd 2.0.49 as the Mozilla guys stated in that it doesn't look like a problem with the browser itself. :) Assume the topology looks like Browser <= HTTPS => Frontends <= HTTP => Backends Assume the Frontends run a reverse proxy configuration with mod_proxy using Apache 2.0.49 to a bunch of Tomcat 4.1.29 or Jetty 4.x servlet containers. The _HTTPS_ connection terminates on the Apaches and mod_proxy opens a new _HTTP_ connection to the backends. Assume the Apaches are at their default settings. Assume user is using either Mozilla 1.6 (Linux or Win32) or Firebird 0.8 (Linux or Win32). Assume the user enters the URL as "https://gamma.fortn.net/basen" without the double quotes. Works, Apache returning HTTP 1.1 responses (no special configuration) Works, Apache returning HTTPS 1.0 responses (Special config "SetEnvIf User-Agent ".*Mozilla/5.0.*" downgrade-1.0") Fails, Apache at its default settings using HTTPS 1.1 and keepalives Reproducible: Always Actual Results: A printout of the redirects with the reload button grayed out. CTRL-R will reload the correct page, though. Expected Results: Don't choke on the redirect. I'll attach a picture of what it looks like and header dumps. The URLs are real so you're welcome to try to reproduce if you feel like it. :-) All three examples work with IE 5.5 (Win32), IE 6.x (Win32), lynx (multiple platforms), links (multiple platforms), wget (multiple platforms) and Safari (OS X). I did try with "SetEnvIf User-Agent ".*Mozilla/5.0.*" nokeepalive" but that made no difference. The attachments are over at mozilla's bugzilla but I can attach them here too if that's needed. Thanks.. Any ideas? --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org