Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 4647 invoked from network); 9 Sep 2000 00:17:23 -0000 Received: from msp-26-164-174.mn.rr.com (HELO localhost.localdomain) (24.26.164.174) by locus.apache.org with SMTP; 9 Sep 2000 00:17:23 -0000 Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by localhost.localdomain (8.9.3/8.9.3) with ESMTP id SAA03118 for ; Fri, 8 Sep 2000 18:15:25 -0500 Received: from taller.eng.sun.com ([129.144.174.34]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA23624; Fri, 8 Sep 2000 17:16:55 -0700 (PDT) Received: from eng.sun.com (florence [129.144.251.146]) by taller.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA22951; Fri, 8 Sep 2000 17:16:54 -0700 (PDT) Message-ID: <39B981B0.D59A471B@eng.sun.com> Date: Fri, 08 Sep 2000 17:17:53 -0700 From: "Craig R. McClanahan" X-Mailer: Mozilla 4.74 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org CC: Z_Tomcat Alias Subject: Re: BugRat Report #92 was closed (apparently by: Craig R. McC References: <0026ACE3.C22202@seagram.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Jonathan Pierce wrote: > Paths on NT are not case sensitive. > Agreed, but that's not the point. Resource paths used in HTTP are case sensitive. > > Only the part of the URL after the /servlet needs to be case sensitive. > How do you figure that? From the point of view of HTTP, the context path and the "/servlet" prefix are part of the resource path -- the protocol makes absolutely no distinction between it and the remainder of the path. If HTTP were a MIcrosoft-only protocol, I'd be in agreement with you. But it's not. Tomcat needs to play by the official specification's rules. > > This also causes a problem when configuring Tomcat to startup as a service if > the app directory parameter is not typed in the correct case. > Is there something so terribly hard about typing it in the correct case when you run into this? :-) > > Can this be changed to support case insensitivity for the part of the part that > precedes the context? > Can it be changed? Sure. Will it be changed? Not in the official distribution, if my -1 counts for anything (which it does). Because this is open source, you are welcome to create yourself a patch to make your version of Tomcat non-standard in this respect. But you're not going to like the performance impact this has on figuring out what webapp a request belongs to, or what servlet to execute. > > Jonathan > Craig McClanahan ==================== See you at ApacheCon Europe ! Session VS01 (23-Oct 13h00-17h00): Sun Technical Briefing Session T06 (24-Oct 14h00-15h00): Migrating Apache JServ Applications to Tomcat