Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 17229 invoked from network); 17 Apr 2002 08:13:22 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 17 Apr 2002 08:13:22 -0000 Received: (qmail 10953 invoked by uid 97); 17 Apr 2002 08:13:28 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 10937 invoked by uid 97); 17 Apr 2002 08:13:28 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 10926 invoked from network); 17 Apr 2002 08:13:27 -0000 Message-ID: <008a01c1e5e7$e28b4a70$a301a8c0@tzida.fhkarlsruhe.de> From: "Andreas Junghans" To: "Tomcat Developers List" References: <20020417055000.52067.qmail@icarus.apache.org> Subject: Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets DefaultServlet.java Date: Wed, 17 Apr 2002 10:13:53 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi Bill, > billbarker 02/04/16 22:49:59 > > Modified: catalina/src/share/org/apache/catalina/core > ApplicationHttpRequest.java > catalina/src/share/org/apache/catalina/servlets > DefaultServlet.java > Log: > Attempt to port the 3.3.x logic to 4.x. > > This fixes the examples in bug #8092. I don't know what else it breaks (so I'm not porting to the 4.0 branch). I think that this is OK, but feel free to -1 if I'm breaking something that I shouldn't be. thanks for the fix, it seems to correct all issues I encountered :-). Your solution is much more elegant (and less intrusive) than what I proposed. I never thought of just swallowing the servlet_path attribute when doing a forward, but it doesn't seem to violate the spec or create any obvious problems. Many thanks again, Andreas -- To unsubscribe, e-mail: For additional commands, e-mail: