Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <39BDA9C0.EA548DF@eng.sun.com>
Date: Mon, 11 Sep 2000 20:57:52 -0700
From: "Craig R. McClanahan" <Craig.McClanahan@eng.sun.com>
MIME-Version: 1.0
To: tomcat-dev@jakarta.apache.org
Subject: Re: Case Sensitivity in URLs (was RE: BugRat Report #92 was  
 closed(apparently by: Craig R.)
References: <704ECFDA88B3D311B5F000A0C959E5B601FBC8@adobo.c2labs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Peter V. Gadjokov" wrote:

> It is allowed
> by the RFC,

But not, it would appear, by the servlet spec.  See section 10 of the
servlet 2.2 spec (or section 11 of the 2.3 draft currently in public
review).  You won't find the words "case sensitive" or "case insensitive" in
this section, but trying to read silence == permission into this it a real
stretch, given the description of the way that path mapping matching works,
and given the fact that the HTTP/1.1 spec (with the now-famous "SHOULD be
case-sensitive" wording :-) is cited as an underlying reference.

If you wish to lobby for a change so that the servlet spec would allow
case-insensitive matches, that is actually pretty timely at the moment --
since the 2.3 spec is currently in public review, it is subject to change,
based on acceptance of the recommendation by the expert group.  Feedback and
suggestions should go to the official feedback address:
servletapi-feedback@eng.sun.com.

Failing the success of that lobbying effort, my -1 on including this
"feature" in the official Tomcat release (even if it defaults to disabled)
remains unchanged.


>
> -pvg
>

Craig McClanahan

PS:  Nothing stops anyone from doing what Costin suggested and posting a
"user contributed patch" someplace.

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat