SEO: 301 www to apex, long-cache static images, add CSP-safe headers

This commit is contained in:
Zac Gaetano 2026-05-04 00:04:21 -04:00
parent 48b4727484
commit e07541a325

View file

@ -2,8 +2,11 @@ import type { NextConfig } from "next";
const nextConfig: NextConfig = { const nextConfig: NextConfig = {
output: "standalone", output: "standalone",
poweredByHeader: false,
compress: true,
images: { images: {
formats: ["image/avif", "image/webp"], formats: ["image/avif", "image/webp"],
minimumCacheTTL: 60 * 60 * 24 * 30, // 30 days
}, },
async headers() { async headers() {
return [ return [
@ -20,6 +23,30 @@ const nextConfig: NextConfig = {
{ key: "X-DNS-Prefetch-Control", value: "on" }, { key: "X-DNS-Prefetch-Control", value: "on" },
], ],
}, },
{
// Long cache for static images served from /public/images.
source: "/images/(.*)",
headers: [
{
key: "Cache-Control",
value: "public, max-age=31536000, immutable",
},
],
},
];
},
async redirects() {
return [
// Force apex hostname. The www host should be terminated upstream
// (Nginx Proxy Manager) and pointed at this app, OR redirected at the
// proxy. This Next-side redirect is a belt-and-braces fallback so that
// www → apex still happens if traffic reaches the app on the wrong host.
{
source: "/:path*",
has: [{ type: "host", value: "www.wilddragon.net" }],
destination: "https://wilddragon.net/:path*",
permanent: true,
},
]; ];
}, },
}; };