deps: cherry-pick 0ef4a0c64b6 from c-ares upstream
Original commit message: gethostbyaddr: fail with `ECANCELLED` for `ares_cancel()` When `ares_cancel()` was invoked, `ares_gethostbyaddr()` queries would fail with `ENOTFOUND` instead of `ECANCELLED`. It seems appropriate to treat `ares_cancel()` like `ares_destroy()`, but I would appreciate review of the correctness of this change. Ref: https://github.com/nodejs/node/issues/14814 Fixes: https://github.com/nodejs/node/issues/14814 PR-URL: https://github.com/nodejs/node/pull/15023 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
This commit is contained in:
parent
4218f1974d
commit
a26be6866b
2
deps/cares/src/ares_gethostbyaddr.c
vendored
2
deps/cares/src/ares_gethostbyaddr.c
vendored
@ -157,7 +157,7 @@ static void addr_callback(void *arg, int status, int timeouts,
|
||||
}
|
||||
end_aquery(aquery, status, host);
|
||||
}
|
||||
else if (status == ARES_EDESTRUCTION)
|
||||
else if (status == ARES_EDESTRUCTION || status == ARES_ECANCELLED)
|
||||
end_aquery(aquery, status, NULL);
|
||||
else
|
||||
next_lookup(aquery);
|
||||
|
Loading…
x
Reference in New Issue
Block a user