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...
> On Apr 10, 2018, at 7:14 AM, Jim Jagielski <j...@jagunet.com> wrote: > > Yeah... this seems related to > > http://svn.apache.org/viewvc?view=revision&revision=1826891 > >> On Apr 10, 2018, at 7:06 AM, Jim Jagielski <j...@jagunet.com> wrote: >> >> % host localhost. >> localhost has address 127.0.0.1 >> localhost has IPv6 address ::1 >> >> What I think is going on is that ab is using ::1 but httpd is just bound on >> 127.0.0.1 >> >> >>> On Apr 9, 2018, at 7:19 PM, Daniel Ruggeri <drugg...@primary.net> wrote: >>> >>> That's interesting. Does your machine bind on both IPv6 and IPv4? I would >>> assume just v4 and you have a localhost as ::1 in your hosts file. Is that >>> the case? >>> -- >>> Daniel Ruggeri >>> >>> On April 9, 2018 4:43:42 PM CDT, Jim Jagielski <j...@jagunet.com> wrote: >>>> OK... if I change the test to use 127.0.0.1 instead of localhost, all >>>> is well. So I'm guessing it is an IPv6 issue... ? >> >
