Dear all,

        Here at DB we are using Tomcat 3.2.3 combined with apache 1.3.20 and 
mod_jk running under redhat 7.1 (+ kernel 2.4.9) to host our mobile
games platform - Unity. I have come across a slightly odd feature of
Tomcat's HTTP response which seems to confuse a couple of the WML
microbrowsers we need to support.

        The basic problem is that the HTTP status line doesn't seem to include 
the textual version of the response i.e. you get back "HTTP/1.1 200" 
instead of "HTTP/1.1 200 OK" etc. I am comparing our current tomcat
build with our previous build which was hosted using JServ. The only
difference between the two responses are the change in the status line
as described plus the addition of a charset clause in the Content-Type

        My first question is which of the three layers of software is generating 
the header when used in this combination - Apache proper, mod_jk, or 
Tomcat itself?

        Is this form of header normal for a hit to a servlet in this setup. What 
do other people see? Do the newer tomcat versions also exhibit this 
behaviour?

        Thanks,

                Geoff.

Reply via email to