Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 99099 invoked from network); 25 Jul 2004 21:44:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 25 Jul 2004 21:44:28 -0000 Received: (qmail 36096 invoked by uid 500); 25 Jul 2004 21:44:26 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 36041 invoked by uid 500); 25 Jul 2004 21:44:25 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 36028 invoked by uid 99); 25 Jul 2004 21:44:25 -0000 X-ASF-Spam-Status: No, hits=1.1 required=10.0 tests=NO_REAL_NAME,UPPERCASE_25_50 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.27.1) with SMTP; Sun, 25 Jul 2004 14:44:24 -0700 Received: (qmail 15021 invoked by uid 50); 25 Jul 2004 21:45:50 -0000 Date: 25 Jul 2004 21:45:50 -0000 Message-ID: <20040725214550.15020.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 28062] - Upload-max-size parameter does not prevent file upload 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=28062 Upload-max-size parameter does not prevent file upload ------- Additional Comments From javageoff@yahoo.com 2004-07-25 21:45 ------- How are you determining that the whole file is being read? Both in current 2.1 HEAD and going back to the 2.1.3 release, it appears that the error is thrown before the MultiPartParser is created, and therefore before parser.getParts is called as confirmed by your stack trace which shows the IOException is being thrown from line 105. See http://svn.apache.org/viewcvs.cgi/cocoon- 2.1/src/java/org/apache/cocoon/servlet/multipart/RequestFactory.java? rev=1.1&only_with_tag=RELEASE_2_1_3&view=auto. In short, I think this bug may be invalid. Geoff Howard