Return-Path: Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: (qmail 48471 invoked from network); 3 Mar 2007 01:28:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2007 01:28:58 -0000 Received: (qmail 2821 invoked by uid 500); 3 Mar 2007 01:29:00 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 2802 invoked by uid 500); 3 Mar 2007 01:29:00 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 2788 invoked by uid 99); 3 Mar 2007 01:29:00 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 17:29:00 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [64.186.168.226] (HELO greenmen.sanasecurity.com) (64.186.168.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 17:28:49 -0800 Received: from localhost (localhost.sanasecurity.com [127.0.0.1]) by greenmen.sanasecurity.com (Postfix) with ESMTP id 610B21155D6; Fri, 2 Mar 2007 17:28:28 -0800 (PST) Received: from greenmen.sanasecurity.com ([127.0.0.1]) by localhost (greenmen.sanasecurity.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57432-05; Fri, 2 Mar 2007 17:28:25 -0800 (PST) Received: from ALIEN.corp.sanasecurity.com (alien.sanasecurity.com [192.168.0.241]) by greenmen.sanasecurity.com (Postfix) with ESMTP id 03FD411556A; Fri, 2 Mar 2007 17:28:25 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mp2] aborting a file upload X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Fri, 2 Mar 2007 17:28:26 -0800 Message-ID: In-Reply-To: <4665E271-F226-43E8-B0D1-D31FFF0680AD@2xlp.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [mp2] aborting a file upload Thread-Index: AcddMiuPxptZI+sAQWOK9VR1fEResAAAKhpw References: <4665E271-F226-43E8-B0D1-D31FFF0680AD@2xlp.com> From: "Matt Williamson" To: "Jonathan Vanasco" Cc: X-Virus-Scanned: by amavisd-new at greenmen.sanasecurity.com X-Virus-Checked: Checked by ClamAV on apache.org Thanks, but I am afraid I do not understand your reply. Should a body with size > POST_MAX cause the upload to fail? Does it send an error back to the client? It did not appear to do either of those things for me. In my situation I want to still process the request, and return ok to the client, just not accept the file! What is a 'fat' apr object? Thanks Matt=20 -----Original Message----- From: Jonathan Vanasco [mailto:jvanasco@2xlp.com]=20 Sent: Friday, March 02, 2007 4:41 PM To: Matt Williamson Subject: Re: [mp2] aborting a file upload On Mar 2, 2007, at 6:37 PM, Matt Williamson wrote: > I have tried POST_MAX on the Apache2::Request creation, but that just=20 > appears to write an error message. I don't know if this will help at all, but its all I can add: I found that while POST_MAX can be modified as the docs say, it can only be lowered (which the docs dont ). To get around those issues, I made a module that i either have other modules register to on startup , or manually code it. It handles conditions/routines to know if i need a 'fat' apr object. If so, my dispatch hander sets a high POST_MAX. if not , it doesn't. That approach solved 90% of my issues , and was very fast to implement. // Jonathan Vanasco