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 22274 invoked from network); 16 Dec 2000 04:14:07 -0000 Received: from femail3.sdc1.sfba.home.com (24.0.95.83) by locus.apache.org with SMTP; 16 Dec 2000 04:14:07 -0000 Received: from C538761A ([24.176.222.130]) by femail3.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20001216041234.BKFQ25762.femail3.sdc1.sfba.home.com@C538761A> for ; Fri, 15 Dec 2000 20:12:34 -0800 Message-ID: <01ce01c06717$4e0568e0$82deb018@intalio.com> From: "Remy Maucherat" To: References: <20001216040330.18903.qmail@locus.apache.org> Subject: Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector HttpResponseBase.java Date: Fri, 15 Dec 2000 20:18:55 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > catalina/src/share/org/apache/catalina/connector > HttpResponseBase.java This may be a dangerous fix, but it's something I wanted to do eventually. I think the mechanism that is used by the servlet wrapper to report errors ends up writing directly on the socket (which forces me to close the connection). If we could use that new error reporting code for everything but uncaught servlet exceptions, that would be cool. Remy