From 268a06268e4838e10891ee5753b197624da37b9a Mon Sep 17 00:00:00 2001 From: Jiachi Liu Date: Thu, 4 Apr 2024 17:35:27 +0200 Subject: [PATCH] Fix status code for /_not-found route (#64058) Fix the status code in static generation metadata for `/_not-found` route, aligning it as 404 for both dev and build `/_not-found` route should still return 404 code as it's reserved as default not found route Closes NEXT-3001 --- test/turbopack-build-tests-manifest.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/test/turbopack-build-tests-manifest.json b/test/turbopack-build-tests-manifest.json index fe6892510978d..956dfbd55ca77 100644 --- a/test/turbopack-build-tests-manifest.json +++ b/test/turbopack-build-tests-manifest.json @@ -2118,7 +2118,8 @@ "app dir - not-found - basic with default runtime should use the not-found page for non-matching routes", "app dir - not-found - basic with runtime = edge should escalate notFound to parent layout if no not-found boundary present in current layer", "app dir - not-found - basic with runtime = edge should match dynamic route not-found boundary correctly", - "app dir - not-found - basic with runtime = edge should use the not-found page for non-matching routes" + "app dir - not-found - basic with runtime = edge should use the not-found page for non-matching routes", + "app dir - not-found - basic should return 404 status code for custom not-found page" ], "failed": [ "app dir - not-found - basic should include not found client reference manifest in the file trace"