Jetty is case sensitive on Linux/Unix, Insensitive on OS X/Windows

I have asked for discussion of this on the dev@jetty.codehaus.org mailing list

as jan has just pointed out to me..... we are case sensitive on all platforms!

The jetty default servlet does check case before servings resources- unless alias checking a has been turned off.

Or are you asking for jetty to be case insensitive on all platforms?

I vote in favor of this, why has it been closed?
It is not just the DefaultServlet that we're talking about here, I think it's the entire getResource() mechanism that should be case sensitive on all OS.
An example:
We have a web application fully exploded on disk (i.e. all .jsp files , no .war).
When directing the http request to a jsp view, we use standard code like:
getServletContext().getRequestDispatcher("/jsp/viewAbcDef.jsp") .
If the file on disk, by mistake, is viewAbcdef.jsp (lowercase d), the request will be handled correctly on Windows - because Jetty can find the file even if the letter case is different. The same request, with the same code, and same files, will fail on Linux.
This makes it very dangerous for those who develop on Windows and deploy on Linux (yes, I am one...)
If you do not want to change default behavior for backward compatibility, at least please add an option to enforce case-sensitivity for those who want it.
And if there already is such an option, my apologies. I searched documentation and googled around, but could not find it.

I'm pretty sure that we do our alias checking, even on getResource.
But I will check, so I've reopened until I can confirm.

Dan, what version of Jetty are you using?

Thanks,
Michael

Michael,
sorry for the very late reply.
I was using 6.1.21.
Now on 7.1.6.
However while trying to prepare a test case as lean as possible, I realized that this seems to occur only via Spring, and not when using RequestDispatcher.forward() directly. When used directly, I see "Aliased resource: file:... ~= file:... which is correct.
Really strange this different behaviour.
In the same web app, a standalone servlet like this:

RequestDispatcher requestDispatcher = request.getRequestDispatcher("/WEB-INF/jsp/viewAbcDef.jsp");
requestDispatcher.forward(request, response);

gives the error - which is correct.

Whereas a Spring ModelAndView("/WEB-INF/jsp/viewAbcDef.jsp") does work regardless of case - which is incorrect.
I stepped into all the Spring inner workings, and it does get exactly to the point where it performs exactly the same forward, with exactly the same data:
requestDispatcher = request.getRequestDispatcher("/WEB-INF/jsp/viewAbcDef.jsp");
requestDispatcher.forward(request, response);

so I don't understand why the different behaviour.
Regardless - consider this closed. I'll investigate this more in my spare time (i.e. never).
Sorry for abusing of your time

Closing as requested

closing resolved issues