tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <rainer.j...@kippdata.de>
Subject Re: bad content type mod_jk 1.2.27
Date Mon, 08 Dec 2008 14:49:08 GMT
marcobalc schrieb:
> Hi,
> 
> no FlushHeader option is not vital: I have tried this option in order to
> solve the problem.
> 
> With o without this option I have the same problem.
> 
> I attach one request for Excel that return the bad result
> 
> http://www.nabble.com/file/p20893729/logModJk.txt logModJk.txt 

This seems to be an issue with the backend, most likely with the webapp.
It is *not* sending any Header to mod_jk, so the response gets the
default. Is this Excel sheet generated by code (servlet), or is it
simply a static file in your webapp? The URL ends in the suffix .ic, so
if it is a static file, I expect that neither in your web.xml (Tomcat)
nor in the Apache config there is an entry for .ic=application/excel.

Regards,

Rainer

> Rainer Jung-3 wrote:
>> Hi Marco,
>>
>> marcobalc schrieb:
>>> i all,
>>>
>>> I have a problem with 
>>>
>>> tomcat 6.0.18 
>>> Apache/2.2.9
>>> mod_jk/1.2.27
>>>
>>> Some times the content-type sent from my tomcat is ignored and the
>>> response have content type text/plain.
>>>
>>> For this reason some servlet that should return excel file and set the
>>> contentType("application/excel") have bad beahviour on the browser: the
>>> file was not recognized as excel but as binary generic file.
>>>
>>> The problem is present also for normal html page: some times the HTML
>>> source are displayed on the browser.
>>>
>>> I have found that mod_jk 1.26 was affected by this problem but the
>>> problem was fixed
>>>
>>> http://markmail.org/message/jk7ssoyhuadvjvh3
>>>
>>>
>>> This is my configuration:
>>>
>>> #Load mod_jk module
>>> LoadModule jk_module modules/mod_jk.so
>>>
>>> #Where to find workers.properties
>>> JkWorkersFile conf/workers.properties
>>>
>>> #Where to put jk logs
>>> JkLogFile logs/mod_jk.log
>>>
>>> #Set the jk log level
>>> JkLogLevel debug
>>>
>>> # Select the log format
>>> JkLogStampFormat "[%a %b %d %H:%M:%S %Y]"
>>>
>>> #JkOptions indicate to send SSL KEY SIZE
>>> JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
>>> +FlushHeader
>>>
>>> #JkRequestLogFormat set the request format
>>> #JkRequestLogFormat "%w %V %T"
>>>
>>> # Send /ROOT to worker named “myworker”
>>>
>>> #JkMount /* myworker
>> Is the FlushHeader option vital for your application? Can you check, if
>> it also occurs without that option?
>>
>> Since you have log level debug: do you have a JK log file which contains
>> at least one request, which resulted in this wrong behaviour?
>>
>> How easy can you reproduce?
>>
>> Regards,
>>
>> Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message