On 11/9/05, Garner, Shawn <[EMAIL PROTECTED]> wrote: > It isn't from a link necessarily. > Usually it is because somebody typed it in instead of using the link we > provided. > Usually they have caps on or they somehow capitalize one letter. > I'd like to catch the people that are doing this and have them get the right > page. <snip/>
The task of emulating the kind of case insentivity you are talking about can be fairly easily handled at the webserver. Since you mentioned you're using IIS, maybe you can try URLSpellCheck for IIS (I haven't used it)? [1] And, ofcourse, if you move to Apache, mod_speling [2] (with a single l for added humor) has been around for ages. -Rahul [1] http://www.port80software.com/products/urlspellcheck/ [2] http://httpd.apache.org/docs/2.0/mod/mod_speling.html > > Shawn D. Garner > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper > Sent: Wednesday, November 09, 2005 5:31 PM > To: user@struts.apache.org > Subject: Re: [OT] Web application context case > > Garner, Shawn wrote: > > I have a struts webapp on JRun tied to IIS. > > > > Anyway our application's context root is all lowercase for example /webapp > > > > But the stats for our site in the IIS logs say we're getting 404 page not > > found errors for the same context only with different case variations. > > > > So for /WEBAPP, /WebApp for example they get a 404 page not found. > > > > I tried to google this but was unable to find anything on cases and > context > > root. > > > > Anyone know how I can get my webapp to catch the other variations of > > lower/upper case letters? > > URLs are case sensitive so, short of deploying your web application > multiple times, you can't. You'll need to identify where these incorrect > requests originate, and fix any broken links. > > L. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
