On 7/18/25 13:35, Randolf Richardson via modperl wrote:
On Jul 17, 2025, at 1:32PM, Alex Aminoff wrote:
I have written up a description and replication code here:
http://back.nber.org/sys-admin/apache2_upload_bug.html
Is this something anyone else has seen?
Hi, Alex. Yes, this is a known p
> On Jul 17, 2025, at 1:32PM, Alex Aminoff wrote:
> > I have written up a description and replication code here:
> >
> > http://back.nber.org/sys-admin/apache2_upload_bug.html
> >
> > Is this something anyone else has seen?
>
> Hi, Alex. Yes, this is a known problem that has been discussed on the
On Thu, 17 Jul 2025 13:31:29 -0400
Alex Aminoff wrote:
Hi Alex,
>
> I am seeing some very suprising behavior with calling ->upload on a
> Apache2::Request object (with use Apache2::Upload).
See this thread about the problem and how to solve it :
https://lists.apache.org/thread/1wno98spl8gzf
On Jul 17, 2025, at 1:32 PM, Alex Aminoff wrote:
> I have written up a description and replication code here:
>
> http://back.nber.org/sys-admin/apache2_upload_bug.html
>
> Is this something anyone else has seen?
Hi, Alex. Yes, this is a known problem that has been discussed on the mod_perl
an
I've been down this road. If wrapping $r->upload() in an eval block
doesn't solve the problem, it's likely that you need to upgrade
libapreq2 to v2.18 (or newer):
https://www.inter-corporate.com/kb/internal-apreq-error.pl
If your Linux distribution doesn't include
I am seeing some very suprising behavior with calling ->upload on a
Apache2::Request object (with use Apache2::Upload). It appears that if
the user did not click and select a file to upload, that is to say left
the field empty, the server stops processing the
perl code and immediately sends
