You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead, it should pick the first non-link-local address. It is extremely unlikely that you want to listen to a link-local address (starting with fe80::). And in the unlikely case that you do, you certainly would call with options.all to get all resolutions.
What alternatives have you considered?
We could alter all client code to always add options.all and filter, but it seems like node is the correct way to fix this once and for all.
What is the problem this feature will solve?
Naive calls to createServer happily resolve host names to link-local addresses, which then fail to listen:
What is the feature you are proposing to solve the problem?
DNS lookup randomly picks the first available entry
if there are multiple addresses returned by getaddrinfo
Instead, it should pick the first non-link-local address. It is extremely unlikely that you want to listen to a link-local address (starting with
fe80::
). And in the unlikely case that you do, you certainly would call withoptions.all
to get all resolutions.What alternatives have you considered?
We could alter all client code to always add
options.all
and filter, but it seems like node is the correct way to fix this once and for all.Related issues
The text was updated successfully, but these errors were encountered: