in reply to Apache2::Request Internal apreq error

Hello evergreen,

My answer is not Perl related but my troubleshooting approach on this would be to capture a tcpdump (LinuxOS) if you are running on (WindowsOS) wireshark. By doing so you will see the package arriving and you will explicitly see what is the reply/error back.

Update: From the documentation Apache2::Request/param this should give more data:

$req->args_status(1); # set error state for query-string parser ok $req->param_status == 1; $foo = $req->param("foo"); ok $foo == 1; eval { @foo = $req->param("foo") }; ok $@->isa("Apache2::Request::Error"); undef $@; eval { my $not_found = $req->param("non-existent-param") }; ok $@->isa("Apache2::Request::Error"); $req->args_status(0); # reset query-string parser state to "success"

Hope this helps, BR.

Seeking for Perl wisdom...on the process of learning...not there...yet!

Replies are listed 'Best First'.
Re^2: Apache2::Request Internal apreq error
by evergreen (Novice) on Mar 15, 2019 at 02:47 UTC
    Thanks thanos1983, I tried tcpdump and Wireshark, but the content of the post requests looks good and the multi-part attachments are there, but somehow it is not being parsed.

    I also see this in apache error log:
    [Thu Mar 14 18:40:04 2019] [error] [client 17.108.244.6] (70008)Partia +l results are valid but processing is incomplete: ap_get_brigade fail +ed during prefetch [Thu Mar 14 18:40:04 2019] [error] Internal apreq error
    Will update here if I find anything.