tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: Apache2, Tomcat5.5, mod_jk and HTTP content-type
Date Tue, 30 Jan 2007 08:40:08 GMT
Hi Joe,

what is your configuration?

1) If Tomcat serves the request (i.e. mod_jk forwards it), the 
jsessionid should not be a problem, because tomcat should generate the 
Content-Type header.

2) If Apache serves the request, you should get a "Not Found", because 
it doesn't strip the jsessionid.

So basically I don't understand your observation (although I didn't try 
by myself). If 2) is the problem, I'm actually thinking about an option 
to strip jsessionid's via mod_jk from static content.



Joe Pemberton wrote:
> I'm trying to connect Apache2 with mod_jk to Tomcat5.5.
> Almost everything seems to work.  However, if I have cookies disabled,
> Tomcat will rewrite all urls to include ;jsessionid=XXXXXXXXX (which is I
> want and expect).  Unfortunately, it seems as though Apache2 insists on
> determining the content-type of the response based on the extension of the
> file requested.  This means that:
> if i request "/myservlet/index.html"
>  I get "Content-Type: text/html; charset=UTF-8"
> if i request "/myservlet/index.html;jsessionid=12341243123412341234"
>  I get "Content-Type: text/plain; charset=UTF-8"
> Obviously, this is a problem.  I looked through the apache docs and the
> mod_jk docs, but I didn't find a way to disable this behavior.  I could
> possibly set the DefaultType directive to "text/html", but this would leave
> .gif/.jpg/.css/etc broken.
> I also didn't find much through google.  Any pointers would be greatly
> appreciated.
> -Joe

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message