RFC: Set 404 Revalidate timer to 900 seconds.

[theodesp]

Tasks

• I have signed a Contributor License Agreement (CLA) with WP Engine.
• If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• I have written and included a comprehensive changeset to properly document the changes I've made.

Description

Sets the default ISR revalidate timer on 404 pages.

Closes #1580

Related Issue(s):

Testing

1. Checkout and Build the project.
2. Run the project in production mode (npm run start) vs in dev mode (npm run dev)
3. Run a curl command that will tigger a 404 response.
4. You should see the following header in cache-control:
   Cache-Control: s-maxage=900, stale-while-revalidate

Screenshots

Before

❯ curl -vvv http://localhost:3000/222 | grep cache-control
...
>
< HTTP/1.1 404 Not Found
< x-using: faust
< x-nextjs-cache: HIT
< Cache-Control: s-maxage=31536000, stale-while-revalidate
< ETag: "inm7ps8d27200"
< Content-Type: text/html; charset=utf-8
< Content-Length: 2592
< Vary: Accept-Encoding
< Date: Thu, 09 Nov 2023 12:28:23 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5

After

❯ curl -vvv http://localhost:3000/222 | grep cache-control
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 127.0.0.1:3000...
* Connected to localhost (127.0.0.1) port 3000 (#0)
> GET /222 HTTP/1.1
> Host: localhost:3000
> User-Agent: curl/8.1.2
> Accept: */*
>
< HTTP/1.1 404 Not Found
< x-using: faust
< x-nextjs-cache: HIT
< Cache-Control: s-maxage=900, stale-while-revalidate
< ETag: "7hstphb9w0200"
< Content-Type: text/html; charset=utf-8
< Content-Length: 2592
< Vary: Accept-Encoding
< Date: Thu, 09 Nov 2023 12:33:07 GMT
< Connection: keep-alive
< Keep-Alive: timeout=5
<
{ [2592 bytes data]

Documentation Changes

Dependant PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3111854

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[blakewilson]

@theodesp You may want to update your testing instructions to mention that the user needs to also:

1. Build the example project
2. Run the project in production mode (npm run start) vs in dev mode (npm run dev)

[blakewilson]

Let's add back the carrots to the example project's package.json but other than that, this looks good to go! Nice work @theodesp