That was my knee-jerk reaction, too, but after digging, I saw that win32
really shouldn't be affected.
On 11/16/2016 4:09 PM, Steve Hay wrote:
> On 15 November 2016 at 09:26, Issac Goldstand wrote:
>> Hi all,
>>
>> Someone (finally) noticed that apreq's test suite isn't
Yes, if we go through with this. The mod_apreq2 stuff is in httpd.
However I just realized that although it's been in trunk for years now,
it's never been backported to the 2.4.x branch. I'm not sure why, and
my google-fu isn't finding relevant discussion on dev@httpd.
When I initially took a
On 15 November 2016 at 09:26, Issac Goldstand wrote:
> Hi all,
>
> Someone (finally) noticed that apreq's test suite isn't compatible with
> Apache 2.4 and requested a change. Given that we haven't released an
> updated apreq in nearly 6 years, I'm inclined to make/test the
Given that the C was (finally) merged into httpd years ago, and given
that there are no proposed code changes, I'd say that's not such a bad
idea...
I've become a bit rusty in Perl (and even with apreq) over the years,
but IIRC, all of the Perl glue is in
Honestly, I've no clue. The plan is just to add a few checks with
mod_version (if available) to deal with the 2.2/2.4 config syntax
changes, and the changes so far seem to only be in the test suite. I
haven't hit any changes in libapreq itself yet.
I don't have any connection with the Debian
Good news!! No idea why apreq hasn't just been merged into mod_perl after
all these years.
A+++
On Nov 15, 2016 3:27 AM, "Issac Goldstand" wrote:
> Hi all,
>
> Someone (finally) noticed that apreq's test suite isn't compatible with
> Apache 2.4 and requested a change.