DRAFT WIP fix: Improve TLS error messages for fetch() in local development #5831
+99
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP, see if this improves error output of: cloudflare/workers-sdk#9356
then after can figure out actual right way to do this, but want to understand if this is the underlying issue
When fetch() fails due to TLS certificate errors (e.g., self-signed certs, untrusted CAs), workerd now returns actionable error messages instead of opaque "internal error; reference = ..." responses.
The improved errors:
This helps developers diagnose and fix certificate issues when making HTTPS requests during local development, particularly when connecting to servers with self-signed certificates.