NotFoundPage incorrectly gives 200 status error instead of 404

Because Redwood is a single-page app, the built-in 404-page web/src/pages/NotFoundPage/NotFoundPage.js is handled by WebPack as a “normal” page, i.e. it’s optimized and becomes a part of the dist/static/js/…chunk.js files during build. This can/could be problematic because it results in a 200 http status code for the 404 page and it also requires JS.

This seems like a good opportunity to take a step forward with Redwood pre-rendering! The goal would be to build NotFoundPage as a separate, static asset. Likely there are other solutions that would work (possible that WebPack already has a config option). But if there’s a way to learn and step toward Redwood having pre-render capability, I suggest that be the preferred option.

[simoncrypta]

Same for GraphQL, I think the web don’t care about HTTP code anymore 😅

[thedavidprice]

Per Core Team Discussion:

• bump this as a priority to post-v1; will be incorporated with SSR solution