The content-type header field in an http response from a servlet running in tomcat but delivered through mod-jk appears to be defined by the apache mime type and extension configuration.
If a servlet sets the content type then the value is not reflected in the response when using mod-jk.
This means that the same servlet will behave differently if delivered through mod-jk or tomcat directly, and that servlets cannot be written that will accept arbitrary extensions in the http request if mod-jk is to be used to deliver them.
This may be a bug or it may be a configuration issue with my hosting
provider. If it is a configuration issue then please tell me what they have to
configure and I wil let them know.
If mod-jk issues should be listed elsewhere the let me know and I will post appropriately.
Regards,
Stuart.
_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
