Re: HTTPd Devs Considered Harmful to Apache2::Request users

Simply put, 2.17 was a fraudulent release according to HTTPd's own rules for RM's. Under no circumstances may an RM unilaterally disable any component of the test suite without notifying the remainder of the PMC *on list*, because it is simply a deceptive practice for the rest of the group to have

Re: HTTPd Devs Considered Harmful to Apache2::Request users

Would you trust any of them at this point? I have a copy of svn trunk. I will never use anything they release, no matter what they call it. Joe Schaefer, Ph.D. Orion - The Enterprise Jamstack Wiki 954.253.3732

Re: HTTPd Devs Considered Harmful to Apache2::Request users

So it will be moved to retired I assume or are they going to break their own rules and purge it altogether? On Sun, Feb 18, 2024, 3:33 PM Joe Schaefer wrote: > 2.18 will never be released. They are shutting down the project. > > Joe Schaefer, Ph.D. > > Ori

Re: HTTPd Devs Considered Harmful to Apache2::Request users

2.18 will never be released. They are shutting down the project. Joe Schaefer, Ph.D. Orion - The Enterprise Jamstack Wiki 954.253.3732 On Sun, Feb 18, 2024 at 4:32 PM Mithun Bhattacharya wrote: > Could you clar

Re: HTTPd Devs Considered Harmful to Apache2::Request users

Could you clarify this - 2.17 has a critical bug and 2.18 is about to come out which doesn't have a good enough patch so how would trunk be any better? Also how is this passing make test or were the test cases modified to make the bug pass ? On Sun, Feb 18, 2024, 1:12 PM Joe Schaefer wrote: > T

Re: HTTPd Devs Considered Harmful to Apache2::Request users

You are welcome, colleague! Keep in mind the SoBs are threatening to release 2.18 as we speak, but like everything else they do, it’s a dog and pony show in a Potemkin Village. They simply are too lazy, inept, and mendacious to execute. Use trunk, while it still exists. Joe Schaefer, Ph.D.

Re: HTTPd Devs Considered Harmful to Apache2::Request users

Trunk is the safe bet. Joe Schaefer, Ph.D. Orion - The Enterprise Jamstack Wiki 954.253.3732 On Sun, Feb 18, 2024 at 2:11 PM Mithun Bhattacharya wrote: > So is there a cleaner/saner version of libapreq2 or is t

Re: HTTPd Devs Considered Harmful to Apache2::Request users

Also thank you for the library ! On Sun, Feb 18, 2024, 1:11 PM Mithun Bhattacharya wrote: > So is there a cleaner/saner version of libapreq2 or is the 2012 version > better ? > > On Sun, Feb 18, 2024, 12:58 PM Joe Schaefer wrote: > >> For the past 25 years, I have been the lead developer of the

Re: HTTPd Devs Considered Harmful to Apache2::Request users

So is there a cleaner/saner version of libapreq2 or is the 2012 version better ? On Sun, Feb 18, 2024, 12:58 PM Joe Schaefer wrote: > For the past 25 years, I have been the lead developer of the libapreq2 > subproject within the Apache HTTPd Server Parent Project. The original idea > of libapreq

HTTPd Devs Considered Harmful to Apache2::Request users

For the past 25 years, I have been the lead developer of the libapreq2 subproject within the Apache HTTPd Server Parent Project. The original idea of libapreq as a safe/performant HTML form and Cookie parsing library came out of a collaboration between Lincoln Stein and Doug MacEachern in the late