Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 42024 invoked from network); 14 Sep 2000 11:57:30 -0000 Received: from unknown (HELO infoserver.develop.com) (63.111.243.12) by locus.apache.org with SMTP; 14 Sep 2000 11:57:30 -0000 Received: from yossarian (ppp-2-35.cvx3.telinco.net [212.1.145.35]) by infoserver.develop.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id S6MXLT1S; Thu, 14 Sep 2000 04:55:59 -0700 From: "Kevin Jones" To: "Tomcat-Dev" Subject: Garbage is response stream Date: Thu, 14 Sep 2000 12:54:06 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I'm not sure where to report this but here seems as good a place as any. I'm using Tomcat (3.2b3 approx) with Apache and ajpv12 (I think - this is what is in my tomcat.conf file). This is on Win2K and the ApacheModuleJServ.dll I'm using is dated 31st July 2000. If I use Tomcat stand-alone then I have no problem, but if I use Tomcat with Apache I get garbage in the output stream. An example, I have a JSP page that produces XML (but the problem is there for any response type), if I go direct to Tomcat (on 8080) then I get this - HTTP/1.0 200 OK Content-Type: text/xml Servlet-Engine: Tomcat Web Server/3.2 beta 3 (JSP 1.1; Servlet 2.2; Java 1.3.0; Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.) Don Box 555-2137 etc... If I use Tomcat/Apache I get this HTTP/1.1 200 OK Date: Thu, 14 Sep 2000 11:41:15 GMT Server: Apache/1.3.12 (Win32) tomcat/1.0 Servlet-Engine: Tomcat Web Server/3.2 beta 3 (JSP 1.1; Servlet 2.2; Java 1.3.0; Windows 2000 5.0 x86; java.vendor=Sun Microsystems Inc.) Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Transfer-Encoding: chunked Content-Type: text/xml 13b Don Box 555-2137 etc Notice the 13b at the start of the response body - this number is random, but some value is always there. So - is this s known problem that has been fixed in the latest version of the connector? or is it a bug that I should report via BugTrack? Thanks, Kevin Jones DevelopMentor www.develop.com