On 2/15/06, Joe Schaefer <[EMAIL PROTECTED]> wrote:
The web app in question uses:
$session{req} = Apache2::Request->new($r, POST_MAX => 1024 * $session{setting}{maxAttachmentSize});
With a max AttachmentSize of a meg, that gives me a gig. And when I do the math, I get:
POST_MAX = 1024 * 1000000
so that when I add:
APREQ2_ReadLimit 1024M
to the apache config, everything picks up fine.
Is this a "Crazy" number to have there?
Joe Schaefer <[EMAIL PROTECTED]> writes:
In particular, your POST_MAX argument. You'll get this error
if that's larger than 64M.
The web app in question uses:
$session{req} = Apache2::Request->new($r, POST_MAX => 1024 * $session{setting}{maxAttachmentSize});
With a max AttachmentSize of a meg, that gives me a gig. And when I do the math, I get:
POST_MAX = 1024 * 1000000
so that when I add:
APREQ2_ReadLimit 1024M
to the apache config, everything picks up fine.
Is this a "Crazy" number to have there?
--
Mike Lieman
Client Services of New York, L.L.C.
[EMAIL PROTECTED]
