Re: Fix for ab defect

Am 05.03.2018 um 15:48 schrieb Yann Ylavic: I meant that before the patch, "ab" already succeeded for (e.g.) https://localhost/ or https://192.168.x.x/ that is if the connect is quick enough to not trigger the bug (though it's not necessarily the case in local networks either). This is

Re: Fix for ab defect (was: [VOTE] Release httpd-2.4.31)

On Mon, Mar 5, 2018 at 3:16 AM, Daniel Ruggeri wrote: > >> -Original Message- >> From: Yann Ylavic [mailto:ylavic@gmail.com] >> Sent: Sunday, March 04, 2018 5:09 PM [] >> In this case though, this is not exactly "100% failure" in any >> circonstances, for

RE: Fix for ab defect (was: [VOTE] Release httpd-2.4.31)

> -Original Message- > From: Yann Ylavic [mailto:ylavic@gmail.com] > Sent: Sunday, March 04, 2018 5:09 PM > To: httpd-dev <dev@httpd.apache.org> > Subject: Re: Fix for ab defect (was: [VOTE] Release httpd-2.4.31) > > On Sun, Mar 4, 2018 at 11:4

Re: Fix for ab defect (was: [VOTE] Release httpd-2.4.31)

On Sun, Mar 4, 2018 at 11:48 PM, Daniel Ruggeri wrote: > > I'd like to ask a followup question... how do we catch this in the > test suite? With this (100% failure), ab still returns a 0 exit code. > It *does* at least give the error message to STDERR. Perhaps we > should

RE: Fix for ab defect (was: [VOTE] Release httpd-2.4.31)

t: Sunday, March 04, 2018 1:25 PM > To: li...@rhsoft.net > Cc: httpd-dev <dev@httpd.apache.org> > Subject: Fix for ab defect (was: [VOTE] Release httpd-2.4.31) > > On Sat, Mar 3, 2018 at 10:51 PM, Yann Ylavic <ylavic@gmail.com> wrote: > > On Sat, Mar 3, 2018 at 6

Fix for ab defect (was: [VOTE] Release httpd-2.4.31)

On Sat, Mar 3, 2018 at 10:51 PM, Yann Ylavic wrote: > On Sat, Mar 3, 2018 at 6:40 PM, li...@rhsoft.net wrote: >> >> -1 >> >> "ab" no longer can benchmark https urls, same build-spec and environment >> (Fedora 26 and 27) > > Hmm, looks like 2.4 is missing