Return-Path: 
 <tomcat-dev-return-5283-qmlist-jakarta-archive-tomcat-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org
Received: (qmail 67316 invoked from network); 11 Feb 2002 01:24:49 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 11 Feb 2002 01:24:49 -0000
Received: (qmail 11041 invoked by uid 97); 11 Feb 2002 01:24:49 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org
Received: (qmail 11000 invoked by uid 97); 11 Feb 2002 01:24:48 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 10989 invoked from network); 11 Feb 2002 01:24:48 -0000
Message-ID: <2590403.1013390679930.JavaMail.jpl@remotejava>
Date: Mon, 11 Feb 2002 02:24:39 +0100 (CET)
From: Jan Ploski <jpljpl@gmx.de>
To: tomcat-dev@jakarta.apache.org
Subject: Error: 304. Apparent bug in 3.3a ErrorHandler code
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hello,

I just stumbled upon a show-stopper problem with Tomcat 3.3a and Apache
mod_jk. When refreshing JSPs that referenced static resources (i.e. a CSS
stylesheet or images), from time to time junk would appear at the top
of the page, saying "Error: 304... Location: <page address>". The said
static resources would not load and the browser would appear to hang
indefinitely.

I tracked the problem to the method StatusHandler.doService
defined in share/org/apache/tomcat/modules/generators/ErrorHandler.java
When the 304 (Not Modified) condition is encountered, this method
generates a message body with the above mentioned "junk" and returns
it to mod_jk.

RFC 2068 states:

   "If the client has performed a conditional GET request and access is
   allowed, but the document has not been modified, the server SHOULD
   respond with this status code. The response MUST NOT contain a
   message-body."

Replacing Tomcat's vanilla ErrorHandler with my own clone with the
whole message body generating block omitted if sc == 304 eliminated
the problem.

Interestingly, the bug could only be demonstrated with mod_jk + Tomcat,
but not when I was using Tomcat alone as a web server.

Can anyone confirm the above observations? If I am correct, what is
the official procedure to submit bug reports and fixes?

Take care -
JPL


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>