From ea322ffecb062feac1d95953bcecbf17fd722904 Mon Sep 17 00:00:00 2001 From: "Alejandro E. Rendon" Date: Fri, 31 Jul 2026 06:14:36 -0500 Subject: [PATCH] Update fetch behavior in certificate registry: Changed fetch cache strategy from 'no-store' to 'force-cache' to support static export and prevent dynamic rendering issues during prerendering. This adjustment ensures that each build issues a fresh request while maintaining cacheability. --- src/lib/certificate-registry.ts | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/lib/certificate-registry.ts b/src/lib/certificate-registry.ts index 3f5267e..bde8b5b 100644 --- a/src/lib/certificate-registry.ts +++ b/src/lib/certificate-registry.ts @@ -143,8 +143,9 @@ async function fetchCertificateRegistry(): Promise> { } const response = await fetch(url, { - // Build-time only; avoid Next Data Cache surprises across rebuilds. - cache: "no-store", + // Static export requires a cacheable fetch — `no-store` forces dynamic rendering + // and fails prerender. Each `next build` still issues a fresh request. + cache: "force-cache", redirect: "follow", headers: { // Some Drive edges return an HTML interstitial without a browser-like UA.