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 55965 invoked from network); 1 Dec 2000 00:20:00 -0000 Received: from lukla.sun.com (192.18.98.31) by locus.apache.org with SMTP; 1 Dec 2000 00:20:00 -0000 Received: from centralmail1.Central.Sun.COM ([129.147.62.10]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA01001 for ; Thu, 30 Nov 2000 17:20:00 -0700 (MST) Received: from esun1as-mm. (esun1as-mm.Central.Sun.COM [129.147.34.144]) by centralmail1.Central.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with SMTP id RAA07371 for ; Thu, 30 Nov 2000 17:20:00 -0700 (MST) Received: from eng.sun.com by esun1as-mm. (SMI-8.6/SMI-SVR4) id RAA26630; Thu, 30 Nov 2000 17:32:54 -0700 Message-ID: <3A26EF03.DE0820A9@eng.sun.com> Date: Thu, 30 Nov 2000 16:21:23 -0800 From: "Craig R. McClanahan" X-Mailer: Mozilla 4.75 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: Catalina-4M5 question: parameters? References: <20001129155319.A5211@sterlingplanet.com> <3A258303.8788E24E@eng.sun.com> <20001130182730.A20794@sterlingplanet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Matthew L Daniel wrote: > > To my knowledge, this is not a known issue. In fact, I've got tons of stuff > > that > > depends on request parameters working just fine in 4.0. I would be very > > interested > > in a simple test case that can reproduce what you're seeing. > > I have included a jar (the java needs to be recompiled, so not a .war) of > the stuff I am using, and I tossed in my Catalina server.xml for good measure. > > For completeness, I also tested the examples.war that comes with Catalina, > and the snoop.jsp doesn't work there either. Same output: > > Query string: /examples/jsp/snp/snoop.jsp? > There was a bug introduced in recent nightly builds because of some performance optimization work being done on the HTTP/1.1 connector. This was patched earlier today, and the fix will be in tonight's nightly build. AFAIK this stuff works correctly on the milestone 4 build. Craig McClanahan