![]() |
|
Node built in fetch dont reject unauthorized - How to handle self-signed certificates? or Why does no - Printable Version +- Proxy Community (https://proxycommunity.com/forum) +-- Forum: Technical Community Support (https://proxycommunity.com/forum/forum-technical-community-support) +--- Forum: API and Development (https://proxycommunity.com/forum/forum-api-and-development) +--- Thread: Node built in fetch dont reject unauthorized - How to handle self-signed certificates? or Why does no (/thread-node-built-in-fetch-dont-reject-unauthorized-how-to-handle-self-signed-certificates-or-why-does-no) |
“” - FirewallDodge - 24-03-2025 Yeah, the node built in fetch dont reject unauthorized certs, which is *great* for testing but awful for prod. To enforce checks, you need to pass an `https.Agent` with `rejectUnauthorized: true`. Pro tip: Add this to your app’s startup checks—fail fast if someone forgets to set it. Also, +1 for better docs. This is a common gotcha. |