Nick Mathewson f89168e7ea Make test for bufferevent_connect_hostname system-neutral
Previously, the be5_outcome field for the dns error would be set to
something dependent on our system resolver.  It turns out that you
can't rely on nameservers to really give you an NEXIST answer for
xyz.example.com nowadays: too many of them are annoyingly broken and
like to redirect you to their locked-in portals.  This patch changes
the bufferevent_connect_hostname test so that it makes sure that the
dns_error of be5_outcome is "whatever you would get from resolving
the target hostname"
2010-05-08 19:15:35 -04:00
..
2010-05-08 17:15:52 -04:00
2010-01-23 20:07:05 -05:00
2010-04-23 14:42:25 -04:00
2010-03-05 13:00:15 -05:00
2010-01-12 15:58:36 -05:00