If you have your jkloglevel set to at least info, the modjk log file (whatever
you have it set to) will show the jk version when apache is started or reloaded
-Tony
Sent from my Windows Mobile® phone.
-----Original Message-----
From: Eqbal <eqb...@yahoo.com>
Sent: Saturday, March 07, 2009 2:13 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: mod_jk and 304
Yes I tested on newer version as well, but could not reproduce it there. The
extra bytes are not content and they are always the same regardless of what
resource is requested. How do I find the mod_jk version? It came with the suse
distribution. I tried debug logging, but that didn't spit the version.
----- Original Message ----
From: Len Popp <len.p...@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Saturday, March 7, 2009 9:18:49 AM
Subject: Re: mod_jk and 304
I'm not seeing that problem on my system, but I'm running newer
versions (httpd 2.2.9 and Tomcat 6.0.18). I do recall seeing some
strange 304 responses with 2.0 & 5.5, but it was a while ago and I
don't remember if the problem was extra bytes in the response.
What version of mod_jk are you using? I'm using 1.2.26. If mod_jk is
old you could try updating it. (I know it's a pain to update the whole
web server just to test, but upgrading just mod_jk is easier.)
What are the extra 20 bytes? Are they an actual message body or garbage?
--
Len
On Fri, Mar 6, 2009 at 21:08, Eqbal <eqb...@yahoo.com> wrote:
>
> Some additional info I found on this:
> It seems that combination of mod_deflate and mod_jk is causing the issue. I
> have mod_deflate enabled on apache for css, js files etc. I tried getting a
> css file directly from apache httpd and it didn't have any problems, but if
> the css and js files are in tomcat, apache always seem to append some bytes
> in the message body when there is a 304 response.
>
>
> ----- Original Message ----
> From: Eqbal <eqb...@yahoo.com>
> To: users@tomcat.apache.org
> Sent: Friday, March 6, 2009 3:51:24 PM
> Subject: mod_jk and 304
>
>
> I have tomcat running behind apache http server 2.0 using mod_jk. I have
> noticed that this causes any response to request for files in tomcat that
> return a 304 status code, to also have a 20 byte message body attached to the
> response. This causes our load balancer to think this is an error as
> according to rfc2616 304s must NOT contain any message body.
>
> If I directly go to file in docroot of the webserver, there is no problem,
> but if files are requested from tomcat via mod_jk, it is causing issues.
>
> Anyone faced this issue?
> I am using tomcat 5.5.16, with apache 2.0.59 on suse linux 9.
>
> Thanks
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
