Global certificate bypass flag versus per-request trust policy in Deno
0 reputation · 12 Jul 2023, 19:43 UTC
Deno validates HTTPS server certificates against the system trust store by default. The --unsafely-ignore-certificate-errors flag disables validation globally for every network call in the process, leaving no documented way to relax trust for internal services while keeping strict validation for public APIs.
This creates a binary choice in current Deno releases: enforce system trust everywhere or disable verification for the entire runtime. Applications that must reach both secure public endpoints and internal services with self-signed certificates cannot isolate the relaxation to specific calls.
Is there a planned API for per-request certificate configuration? If not, what constraint prevents isolating trust settings to individual fetch calls?