On 5/31/06 11:35 PM, "Jonathan Vanasco" <[EMAIL PROTECTED]> wrote:
>
> On May 31, 2006, at 10:11 PM, Rebecca Lovelace wrote:
>>
>> Any advice would be appreciated, even if it's just as simple as a
>> recommendation for me to understand the underlying integration.
>
> my advice (apologies if
I've tried numerous variations, but can't get POST_MAX to work properly.
Everything works fine without it.
my $POST_MAX = 1024*1024*10;
my $req = Apache2::Request->new($r, POST_MAX => $POST_MAX);
The error log tells me only "Conflicting information", which seems
exceedingly unhelpful.
Can s
Garrison Hoffman wrote:
I've tried numerous variations, but can't get POST_MAX to work properly.
Everything works fine without it.
my $POST_MAX = 1024*1024*10;
my $req = Apache2::Request->new($r, POST_MAX => $POST_MAX);
The error log tells me only "Conflicting information", which seems
excee
On Thu, 2006-06-01 at 12:59 -0400, Garrison Hoffman wrote:
> I've tried numerous variations, but can't get POST_MAX to work properly.
> Everything works fine without it.
>
> my $POST_MAX = 1024*1024*10;
> my $req = Apache2::Request->new($r, POST_MAX => $POST_MAX);
>
> The error log tells me on
On Jun 1, 2006, at 2:12 PM, Clinton Gormley wrote:
my $req = APR::Request::Apache2->handle($r);
$req->read_limit($Read_Limit);
$req->parse();
if ($req->body_status eq 'Exceeds configured maximum limit') {
die('Body exceeds max upload size');
I have attempted to unsubscribe in all the
correct ways. Please would someone remove me.
Ron
Whitaker
Philip M. Gollucci wrote:
#define APREQ_DEFAULT_READ_LIMIT (64 * 1024 * 1024)
is the default.
Ack! Of course, and I apologize for misleading you.
my $POST_MAX = 1024*1024*10; # Works fine
my $POST_MAX = 1024*1024*100; # Conflicting
Apparently POST_MAX cannot be used to raise APREQ_DEFAULT
Garrison Hoffman wrote:
Philip M. Gollucci wrote:
#define APREQ_DEFAULT_READ_LIMIT (64 * 1024 * 1024)
is the default.
Ack! Of course, and I apologize for misleading you.
my $POST_MAX = 1024*1024*10; # Works fine
my $POST_MAX = 1024*1024*100; # Conflicting
Apparently POST_MAX cannot be us
Philip M. Gollucci wrote:
Apparently POST_MAX cannot be used to raise APREQ_DEFAULT_READ_LIMIT
Yes, thats the
if (ctx->read_limit > bytes && ctx->bytes_read < bytes) {
ctx->read_limit = bytes;
return APR_SUCCESS;
}
OTHERWISE conflicting
Ok, now I understand.
ht
Hi,
As of httpd 2.2.1 $r->status_line()'s code must match $r->status()
and be valid - otherwise, httpd will set it to NULL.
api/status.t tests 4,5 were failing because of this and are now fixed.
I now see no failing tests on FreeBSD.
New Revision: 411028
HTH
--
-
Hi,
httpd 2.0.56 back ported a change from 2.2.1 about not discarding the
Content-Length header.
2.0.55 tested correctly before I started. 2.0.58 now also tests correctly and
is first affected
version in the 2.0.x series. 2.2.x are also correct.
http://svn.apache.org/viewvc?rev=411041&view=r
11 matches
Mail list logo
