undici
undici copied to clipboard
nodejs
Unprecise error message on fetch() to an endpoint with a certificate which was signed by an "unkown" CA
Bug Description
There is a unprecise error message ("fetch failed") on fetch() to an endpoint with a certificate which was signed by an "unkown" CA. If its an custom or internal CA, the fetch() will fail, that seems correct, but the error message ist absolut unprecise. It is therefore very difficult to find the cause.
Reproducible By
fetch() to an enpoint with a certificate which was signed by an "unkown" CA.
An "unkown" CA seems to be an CA which not exist in the default search path for CAs of node. By default node seem to use CA-certificates baked in the build.
Expected Behavior
A useful error message is shown.
Logs & Screenshots
TypeError: fetch failed at Object.fetch (node:internal/deps/undici/undici:11576:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) ...
Environment
Ubuntu 22.04 Node v18.17.0
Does the spec say that we cannot extend the error for a fetch failure, not even through the cause option while constructing the error?
Just checking out as it seems quite often to issues like this are open where the error is hard to understand.
cc: @KhafraDev @ronag
Do I understand you correctly that you think the error message "fetch error" is appropriate here? The user is helpless with this error message!
edit: maybe i misunderstood you and you are talking about displaying more information in the stacktrace. that would be useful :)
Do I understand you correctly that you think the error message "fetch error" is appropriate here? The user is helpless with this error message!
That's the WHATWG specification for fetch(). There is a cause property on the error that reports the actual error that happened.
(unless you are doing cross-platform or isomorphic code, you might have a better experience with undici.request() or good old http.request()).
