Return-Path: Delivered-To: apmail-httpd-bugs-archive@www.apache.org Received: (qmail 38899 invoked from network); 10 Sep 2004 06:58:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Sep 2004 06:58:56 -0000 Received: (qmail 26843 invoked by uid 500); 10 Sep 2004 06:58:53 -0000 Delivered-To: apmail-httpd-bugs-archive@httpd.apache.org Received: (qmail 26802 invoked by uid 500); 10 Sep 2004 06:58:52 -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 26787 invoked by uid 99); 10 Sep 2004 06:58:52 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=NO_REAL_NAME,UPPERCASE_25_50 X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 09 Sep 2004 23:58:50 -0700 Received: (qmail 3156 invoked by uid 50); 10 Sep 2004 07:00:34 -0000 Date: 10 Sep 2004 07:00:34 -0000 Message-ID: <20040910070034.3155.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: bugs@httpd.apache.org Cc: Subject: DO NOT REPLY [Bug 29834] - Apache 1.3 and 2.0 don't handle htaccess files the same way. X-Virus-Checked: Checked 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=29834 Apache 1.3 and 2.0 don't handle htaccess files the same way. ------- Additional Comments From alexis@bookmark.fr 2004-09-10 07:00 ------- I found a similar bug in mod_jk bug database. http://issues.apache.org/bugzilla/show_bug.cgi?id=25055 Same symptoms, but I went deeper in the diagnosis (many configurations tried : Apache 1.3 / 2, mod_jk / mod_jk2, directives in htaccess / httpd.conf ) I can't go any further, and the problem might lay - in the mod_jk/mod_jk2 implementation for Apache 2 - or the Apache 2 API ? This is a SECURITY issue : does anyone know about this ? I can do other tests if necessary. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org