New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPv6 support #586
Comments
🙌 |
The reasoning why this is happening: https://groups.google.com/forum/#!topic/nodejs/0W6UqKy_klk |
I just realised this could be similar to this very old and closed issue: #126 |
Could we do some kind of fallbacking and try/catching?
But that brings quite some overhead of reconnecting. This would have to happen just once, in the beginning, and then Dredd would need to respect the selected strategy for the rest of the requests. Also, this could be an option:
Again, Dredd would remember the selected strategy for all requests within the test run. |
Sometimes name resolution can get weird (looking at you, macOS), so it's easier to just set 127.0.0.1 as the local address. See apiaryio/dredd#586.
Dredd is resolving hostnames always to the IPv4 address. When the backend is listening on IPv6 localhost
::1
and Dredd's server parameter is a hostnamehttp://localhost:3000
the hostname is resolved to the IPv4 address127.0.0.1
and all tests will fail withECONNREFUSED
:Some servers in some constellations are listening on the IPv6 only by default. The workaround solution is to force them to listen on the IPv4 localhost with some equivalent of:
The text was updated successfully, but these errors were encountered: