• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

case insensitive context

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm running IIS 5.0 and Tomcat 5.0.25 on a Win2k server with the ajp13 connector. Requests to http://myserver.com/TEST/ work but requests to http://myserver.com/test/ fail. How can I configure it such that requests to both will work?

I've tried a variety of things including IIS redirects, and settings in the rewrite.properties and uriworkermap.properties but nothing seems to work! Any help would be very much appreciated!
 
Sheriff
Posts: 67749
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is no way to set things up so that the context path is case insensitive.

Seems like a rather odd thing to want to do, but you can approximate it by creating mutliple contexts that point to the same web app on disk, each with the different name that you want to use.

Note that this will create separate web apps, and so things like the application context will not be shared.
[ October 04, 2006: Message edited by: Bear Bibeault ]
 
Brad Carson
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Oh... you're kidding, right?

Well, the context is actually an acronym which is why it was created uppercase but I know the users are going to mess up the url and type it in lowercase which will get them absolutely nowhere.

I find it a little strange that it is Tomcat that throws the 404 when accessing the lowercase context (e.g. http://myserver.com/test) and not IIS (since Tomcat is only configured for the uppercase url).
 
Sheriff
Posts: 13411
Firefox Browser VI Editor Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
IIS is probably the only web/app server out there that doesn't follow the HTTP specs as far as case sensitivity in URLs is concened.
 
Bear Bibeault
Sheriff
Posts: 67749
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My advice? Acronym or not, make it lowercase.

URLs aren't really the place to worry too much about grammatical-correctness.
[ October 04, 2006: Message edited by: Bear Bibeault ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic