Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 14097 invoked from network); 7 Feb 2002 18:53:47 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 Feb 2002 18:53:47 -0000 Received: (qmail 17964 invoked by uid 97); 7 Feb 2002 18:53:13 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 17948 invoked by uid 97); 7 Feb 2002 18:53:12 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 17924 invoked from network); 7 Feb 2002 18:53:12 -0000 Sender: garym@maya.dyndns.org To: "Tomcat Users List" Subject: Re: Error 200? References: <2842759.1013070482091.JavaMail.nobody@db-portal.office> From: Gary Lawrence Murphy X-Home-Page: http://www.teledyn.com Organization: TCI Business Innovation through Open Source Computing Date: 07 Feb 2002 13:52:55 -0500 Message-ID: Reply-To: Gary Lawrence Murphy X-Url: http://www.teledyn.com/ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >>>>> "A" == Anton Brazhnyk writes: A> Headers cant contain blank llines, and I have no idea what your A> client wanted with that "Error 200". Precisely; this error appears to be generated from either Tomcat or Jasper and is not likely in my client's code (it would be highly irregular of them to use numerical codes) Because the error is being emitted across the servlet output stream during the transmission of headers, and because it is wrapped in blank lines, it appears on the page as content. if you do a google search for "JSP Error 200" you will see they are not alone: This appears to be a common problem with JSP pages, so its surprising no one has reported it and that the fix is not common knowledge. My guess is that it is the sort of error that crops up due to mis-configuration and most sites discover the config glitch, fix it, and the code goes away so they never report it. What I'm hoping is someone familiar with the sources can check the tomcat/jasper sources to see if it is in there somewhere (or maybe mod_jk?) as this error is itself an error: It should report to the stderr log, not the servlet output stream. -- Gary Lawrence Murphy TeleDynamics Communications Inc Business Innovations Through Open Source Systems: http://www.teledyn.com "Computers are useless. They can only give you answers."(Pablo Picasso) -- To unsubscribe: For additional commands: Troubles with the list: