Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 76948 invoked from network); 12 Oct 2000 16:45:14 -0000 Received: from brick.eb.com (HELO CHIEC01.eb.com) (208.154.71.2) by locus.apache.org with SMTP; 12 Oct 2000 16:45:14 -0000 Received: by chiec01.eb.com with Internet Mail Service (5.5.2650.21) id <4R1TKSLP>; Thu, 12 Oct 2000 11:44:34 -0500 Message-ID: <4538F96A1478D211BEC40008C7A4CD9D059CF897@chiec01.eb.com> From: rwaldhof@us.britannica.com To: tomcat-user@jakarta.apache.org Cc: Wellington.Lacerda@fao.org Subject: RE: [tomcat-users] Re: Lowercase UPPERCASE Date: Thu, 12 Oct 2000 11:44:30 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0346B.B159A0C0" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0346B.B159A0C0 Content-Type: text/plain; charset="iso-8859-1" How about using a HTTP redirect or a server-side forward or include to map from mIxEd cAsE to lower case? If you've got a webserver in front of tomcat you could probably do that using a plug-in, or you could map all requests on that server to a "case normalizing" servlet by mapping "/" to that servlet and picking up the rest of the URL from the HttpServletRequest.getPathInfo. Or, maybe you could set up a 404 handler within your webserver that is invoked when no other matching resource is found, and attempts to discover the resource using the lowercase version. -----Original Message----- From: Lacerda, Wellington (AFIS) [mailto:Wellington.Lacerda@fao.org] Sent: Thursday, October 12, 2000 11:02 AM To: 'tomcat-user@jakarta.apache.org' Subject: RE: [tomcat-users] Re: Lowercase UPPERCASE Let's go by the numbers: 0. I'm not defining a case sensitivity problem IN TOMCAT. I have a situation here I'd like to know if someone else got or have a solution to. 1. By a LOT I mean GIGABytes of static or dynamic pages pointing to a web app in tomcat 2. YES, I'm using NT. And NO, IT DIDN'T MATTER. 3. When the CONTEXT NAME came in with a different case (lower or UPPER) I get ERRORS. 4. I know the standard approach is being case sensitive and this is NOT a bug. 5. YES I want to make tomcat case INSENSITIVE in order to call /ThIsCoNtExT/something.jsp as /thiscontext/something.jsp and be successful 6. Perl won't work because I have static and dynamic pages, with addresses hardcoded, in databases, perls scripts, C++ CGI, etc. Think about 10 years of web pages ? MANY thanks. Wellington Silva UN/FAO -----Original Message----- From: kenneth topp [mailto:caught@prodigy.net] Sent: Thursday, October 12, 2000 5:28 PM To: 'tomcat-user@jakarta.apache.org' Subject: Re: [tomcat-users] Re: Lowercase UPPERCASE A better approach? you haven't even described the problem: " We're having problems with linking a LOT of static pages with one of our webapps because in those pages sometimes the addresses are in lower sometimes the same addresses are in UPPER case. How can I avoid this case sensitivity problem in TOMCAT ? " You want to make tomcat case insensitive? Does this mean you want to have a file called ThisIsAWebPage.jsp and have tomcat display it if the url ends with: thisisawebpage.jsp ? Is this for external links to non-tomcat served files from pages generated by tomcat? Are you running NT, where the filesystem is case insensitive? What do you mean by "linking a LOT of static pages with one of our webapps"? If you are putting in the link to the static page, it should be the correct case, no? Answer some of these questions, and we will see. I will declare right now: 1) you haven't defined a case sensitivity problem in tomcat. (at least to my eyes) 2) I don't knoww of a case sensitivity problem in tomcat. 3) If you think that keeping all the files random case, and having tomcat hack around to get it to work is a better solution then fixing the files going forward.... The solution that Joakim offered is valid, you should offer a better reason: ie: I cannot clean up all the files; don't have/know perl; company policy; etc. a couple of gigs isn't that much data to run through perl. and if it's turns out to be the right solution, better 2gigs then 20gigs, no? But, please answer the questions above, I think that the list might be able to find a solution and/or post tomcat code to fix this for you. Kenneth Topp --- to unsubscribe: tomcat-user-unsubscribe@jakarta.apache.org for more info: http://jakarta.apache.org/getinvolved/mail.html On Thu, 12 Oct 2000, Lacerda, Wellington (AFIS) wrote: > A couple of GIGAbytes of html ? I need a better approach. > > Anyway there's already a standard running here, but these are legacy pages > (static and dynamic). > > Wellington Silva > UN/FAO > > -----Original Message----- > From: Joakim Verona [mailto:joakim@verona.se] > Sent: Thursday, October 12, 2000 4:17 PM > To: tomcat-user@jakarta.apache.org > Subject: Re: Lowercase UPPERCASE > > hello, > > why not just have a system where you decide evrything is, > for instance, lowercase, > and 1) rename all your files and 2) search/replace all URL:s > with a regexp. > > kind of obvious, so i guess there is some reason why you > dont do this already. > I sometimes have the same problem when people make files on > pc or mac, and my > solution has always been to enforce some type of namming > standard. > > there is less work for the server if it doesnt have to guess > the name also. > > > "Lacerda, Wellington (AFIS)" wrote: > > > > We're having problems with linking a LOT of static pages > with one of our > > webapps because in those pages sometimes the addresses are > in lower > > sometimes the same addresses are in UPPER case. How can I > avoid this case > > sensitivity problem in TOMCAT ? > > > > If not possible, what could be a solution ? Writing an > Interceptor ? Have > > anyone done this before and can share the code ? > > > > Thanks, > > > > Wellington Silva > > UN/FAO > > -- > Joakim Verona > joakim@verona.se > http://www.verona.se/ > ------_=_NextPart_001_01C0346B.B159A0C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [tomcat-users] Re: Lowercase UPPERCASE

How about using a HTTP redirect or a server-side = forward or include to map from mIxEd cAsE to lower case? 

If you've got a webserver in front of tomcat you = could probably do that using a plug-in, or you could map all requests = on that server to a "case normalizing" servlet by mapping = "/" to that servlet and picking up the rest of the URL from = the HttpServletRequest.getPathInfo. Or, maybe you could set up a 404 = handler within your webserver that is invoked when no other matching = resource is found, and attempts to discover the resource using the = lowercase version.

-----Original Message-----
From: Lacerda, Wellington (AFIS) [mailto:Wellington.Lacerda@fao= .org]
Sent: Thursday, October 12, 2000 11:02 AM
To: 'tomcat-user@jakarta.apache.org'
Subject: RE: [tomcat-users] Re: Lowercase = UPPERCASE


Let's go by the numbers:

0.      I'm not defining a = case sensitivity problem IN TOMCAT. I have a
situation here I'd like to know if someone else got = or have a solution to.

1.      By a LOT I mean = GIGABytes of static or dynamic pages pointing to a
web app in tomcat

2.      YES, I'm using NT. = And NO, IT DIDN'T MATTER.

3.      When the CONTEXT = NAME came in with a different case (lower or UPPER)
I get ERRORS.

4.      I know the standard = approach is being case sensitive and this is NOT
a bug.

5.      YES I want to make = tomcat case INSENSITIVE in order to call
/ThIsCoNtExT/something.jsp as = /thiscontext/something.jsp and be successful

6.      Perl won't work = because I have static and dynamic pages, with
addresses hardcoded, in databases, perls scripts, = C++ CGI,  etc. Think about
10 years of web pages ?

MANY thanks.

Wellington Silva
UN/FAO


        =         -----Original = Message-----
        =         From:   kenneth topp [mailto:caught@prodigy.net]=
        =         Sent:   Thursday, October 12, 2000 5:28 PM
        =         To:     = 'tomcat-user@jakarta.apache.org'
        =         Subject:        Re: = [tomcat-users] Re: Lowercase UPPERCASE


        =         A better = approach? you haven't even described the problem:

        =         " We're = having problems with linking a LOT of static pages
with one of our
        =         webapps = because in those pages sometimes the addresses are
in lower
        =         sometimes the = same addresses are in UPPER case. How can I
avoid this case
        =         sensitivity = problem in TOMCAT ? "

        =         You want to = make tomcat case insensitive?  Does this mean
you want to have
        =         a file called = ThisIsAWebPage.jsp and have tomcat display it
if the url
        =         ends = with:  thisisawebpage.jsp ?  Is this for external = links
to non-tomcat
        =         served files = from pages generated by tomcat?  Are you
running NT, where
        =         the = filesystem is case insensitive?  What do you mean by
"linking a LOT of
        =         static pages = with one of our webapps"?  If you are putting
in the link to
        =         the static = page, it should be the correct case, no?

        =         Answer some = of these questions, and we will see.  I will
declare right
        =         now:
        =           1) you = haven't defined a case sensitivity problem in
tomcat.
        =              (at least to my eyes)
        =           2) I = don't knoww of a case sensitivity problem in tomcat.
        =           3) If = you think that keeping all the files random case,
and having
        =              tomcat hack around to get it to work = is a better
solution then
        =              fixing the files going = forward....

        =         The solution = that Joakim offered is valid, you should offer
a better
        =         reason:  = ie: I cannot clean up all the files; don't
have/know perl;
        =         company = policy; etc.

        =         a couple of = gigs isn't that much data to run through perl.
and if it's
        =         turns out to = be the right solution, better 2gigs then
20gigs, no?

        =         But, please = answer the questions above, I think that the
list might be
        =         able to find = a solution and/or post tomcat code to fix this
for you.

        =         Kenneth = Topp
        =         ---
        =          to = unsubscribe: tomcat-user-unsubscribe@jakarta.apache.org
        =          for = more info:
http://jakarta.apache.org/getinvolved/mail.html


        =         On Thu, 12 = Oct 2000, Lacerda, Wellington (AFIS) wrote:

        =         > A couple = of  GIGAbytes of html ? I need a better approach.
        =         >
        =         > Anyway = there's already a standard running here, but these
are legacy pages
        =         > (static = and dynamic).
        =         >
        =         > = Wellington Silva
        =         > = UN/FAO
        =         >
        =         > =       =         -----Original = Message-----
        =         > =       =         From:   Joakim = Verona
[mailto:joakim@verona.se]
        =         > =       =         Sent:   Thursday, = October 12, 2000 4:17 PM
            &= nbsp;   >       =         To:     = tomcat-user@jakarta.apache.org
        =         > =       =         = Subject:        Re: Lowercase = UPPERCASE
        =         >
        =         > =       =         hello,
        =         >
        =         > =       =         why not just have a system = where you decide
evrything is,
        =         > for = instance, lowercase,
        =         > =       =         and 1) rename all your files = and 2)
search/replace all URL:s
        =         > with a = regexp.
        =         >
        =         > =       =         kind of obvious, so i guess = there is some
reason why you
        =         > dont do = this already.
        =         > =       =         I sometimes have the same = problem when
people make files on
        =         > pc or = mac, and my
        =         > =       =         solution has always been to = enforce some
type of namming
        =         > = standard.
        =         >
        =         > =       =         there is less work for the = server if it
doesnt have to guess
        =         > the name = also.
        =         >
        =         >
        =         > =       =         "Lacerda, Wellington = (AFIS)" wrote:
        =         > =       =         >
        =         > =       =         > We're having problems = with linking a LOT
of static pages
        =         > with one = of our
        =         > =       =         > webapps because in = those pages sometimes
the addresses are
        =         > in = lower
        =         > =       =         > sometimes the same = addresses are in UPPER
case. How can I
        =         > avoid = this case
        =         > =       =         > sensitivity problem in = TOMCAT ?
        =         > =       =         >
        =         > =       =         > If not possible, what = could be a solution
? Writing an
        =         > = Interceptor ? Have
        =         > =       =         > anyone done this before = and can share the
code ?
        =         > =       =         >
        =         > =       =         > Thanks,
        =         > =       =         >
        =         > =       =         > Wellington Silva
        =         > =       =         > UN/FAO
        =         >
        =         > =       =         --
        =         > =       =         Joakim Verona
        =         > =       =         joakim@verona.se
        =         > =       =         http://www.verona.se/
        =         >
        =        =20

------_=_NextPart_001_01C0346B.B159A0C0--