On Tue, Apr 10, 2018 at 08:47:03AM -0400, Jim Jagielski wrote:
> My understanding is that this patch was specifically designed
> to address this exact situation, so I am confused why it
> seems to be causing the problem... It's like ab tries ::1,
> doesn't connect and then fails immediately instead of
> then trying 127.0.0.1...

Can you run ab under something strace-like to see what it's trying to 
do?

Since the test suite defaults to v4-only, possibly we should switch the 
test suite to run against http://127.0.0.1:N/ rather than relying on 
localhost resolving properly, though exposing these bugs is a good 
thing.

Regardsm Joe

Reply via email to