On Jul 17, 2025, at 1:32 PM, 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. Regards, Ed
