> On Jul 17, 2025, at 1:32PM, Alex Aminoff <amin...@nber.org> 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 and mod_perl dev mailing lists going back to 2022 and which came to
> a boil in February 2024. Check the mailing list archives to read more about
> the sad state we are in.
>
> Essentially, libapreq 2.17 is broken, as you have discovered, and it should
> not be used, imho. If you can access the svn repository for libapreq, I think
> the trunk might have a fix for the problem you have encountered, but it
> hasn't been officially released as 2.18. Personally, I continue to use an
> older version of libapreq that I know works well.
Compiling libapreq2 v2.18 from SVN sources resolved all these
problems for me, and I've been using it on multiple production
servers (Debian Linux, and each hosting multiple web sites that are
written either partly or entirely in Perl and relying on mod_perl2)
for nearly 10 months now.
If anyone's interested in feedback on libapreq2 v2.18, please take
this as positive feedback -- it resolved all the problems I
encountered in v2.17 and it also has not caused new/other problems.
Randolf Richardson, CNA - rand...@inter-corporate.com
Inter-Corporate Computer & Network Services, Inc.
Beautiful British Columbia, Canada
https://www.inter-corporate.com/
