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 probably why we didn't notice it on manual testing, "ab"-ing external/wan/google servers is not that usual...
FWIW - i noticed the bug on every single https request on the local machine, google.com was only for a reproducer
Concurrency Level: 1 Requests per second: 311.85 [#/sec] (mean)
