Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] war file works on linux but not OS X

Barnet, please provide some more details. What's the URL you're trying to access. Name some examples that work and some that don't work on both platforms.

I bet Joakime is pointing to the right direction. On windows filenames are not case sensitive on *nix (like OSX) they're.

So if you've a URL pointing to a static file in your war like:

But the file's name is actually: StaticFile.html it'll work fine on windows, but not on OSX.

Am 2/28/13 9:31 PM, schrieb Barnet Wagman:
On 2/28/13 1:42 PM, Joakim Erdfelt wrote:
Static DefaultServlet content, served from a war file, is case sensitive.
Where is DefaultServlet content usually specified?  I've generated my
war using Netbeans/gwt and I haven't seen a parameter with this name.


Joakim Erdfelt <joakim@xxxxxxxxxxx <mailto:joakim@xxxxxxxxxxx>> <>
Developer advice, services and support
from the Jetty & CometD experts <> -

On Thu, Feb 28, 2013 at 12:35 PM, Barnet Wagman <bw@xxxxxxxxx
<mailto:bw@xxxxxxxxx>> wrote:

    I've have a war file that works on a linux system but partially
    fails under os x. The WAR contains two html files.  Both are
    accessible under linux but on an os x system, attempting to load
    one of them yields an HTTP ERROR 404.

    I'm using jetty 8.1.8.v20121106 on both systems. I'm running jetty
    embedded in a java app.

    I can't imagine what the difference could be.  Any thoughts on
    this would be appreciated.

    FYI just to be on the safe side, the html filenames are caseless
    (I don't thing this should matter inside a war).


    jetty-users mailing list
    jetty-users@xxxxxxxxxxx <mailto:jetty-users@xxxxxxxxxxx>

jetty-users mailing list

jetty-users mailing list

Back to the top