rsnext/test/e2e/app-dir/app-static/app/stale-cache-serving
Zack Tanner d9531c13c4
Revert "fix: fetch() behavior when "dynamic" is "force-dynamic" (#58735)
Reverts vercel/next.js#58484

The correct way to address this is to use the `fetchCache` segment: https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#fetchcache

There are valid use-cases to want to force a dynamic response but still need fetch caching.

Additionally, this PR updates the docs, since they're incorrect about behavior.

[slack x-ref](https://vercel.slack.com/archives/C042LHPJ1NX/p1691623048477119?thread_ts=1691613915.257239&cid=C042LHPJ1NX)
2023-11-22 18:49:20 +00:00
..
app-page Revert "fix: fetch() behavior when "dynamic" is "force-dynamic" (#58735) 2023-11-22 18:49:20 +00:00
route-handler Revert "fix: fetch() behavior when "dynamic" is "force-dynamic" (#58735) 2023-11-22 18:49:20 +00:00