Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 4084 invoked from network); 4 Oct 2004 09:43:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 4 Oct 2004 09:43:14 -0000 Received: (qmail 9106 invoked by uid 500); 4 Oct 2004 09:43:02 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 9060 invoked by uid 500); 4 Oct 2004 09:43:02 -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 9041 invoked by uid 99); 4 Oct 2004 09:43:02 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 04 Oct 2004 02:43:01 -0700 Received: (qmail 17171 invoked by uid 50); 4 Oct 2004 09:44:29 -0000 Date: 4 Oct 2004 09:44:29 -0000 Message-ID: <20041004094429.17170.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 31523] - Request parameters are not always passed to HttpServlet.service X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31523 Request parameters are not always passed to HttpServlet.service remm@apache.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From remm@apache.org 2004-10-04 09:44 ------- I never got the problem, so I recommend you look into this more. We got a few similar reports like this, but I think every time it ended up being a user error. If you look into the code, and when parameter parsing is done (it is really very simple), you will find your assertion "When iterating over the request parameters (POST) immediately after entering the HttpServlet.service(HttpServletRequest, HttpServletResponse) method the parameters are not always set" doesn't make any sense, and the most likely reason of the parameters not being there is because they haven't been sent properly. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org