Andrew Barton wrote:
I performed one final troubleshooting step which may be important, but I am
not certain. I added the following directive to the access log configuration
for my stand-alone resin instance: "%{Content-Type}o". This provides the
mime type specified in responses from resin to client browsers. Resin is
serving jar files at 'text/html'. This seems incorrect, but I'm not sure
that this would result in the problem I am seeing.
I think this hits the nail on the head. Windows will very often ignore
mime types, but other platforms can be very strict about it. I suspect
the JVM you're using on OS X (that's getting used in all browsers) is
not dealing well with the jar file served in a different content type.
I forget if/how you can tweak the mime settings in resin standalone, but
if you have got the time/knowledge, you could try writing a basic
servlet that sets the correction content type (application/zip? I'm not
sure), and then reads the jar file and serves that. This could allow
you to confirm that it is the content type that's messing up your browser.
--
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com/
p. 1.301.656.5501
e. sergek@xxxxxxxxxxxx
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
