Is Middleware need to be cached? about next.js HOT 5 CLOSED

Hi -- the behavior you're observing relates to the client router cache.

If you'd like to disable the client router cache so that every request hits the server, you can disable it by modifying your next.config.js as follows:

/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    staleTimes: {
      dynamic: 0,
    },
  },
}

module.exports = nextConfig

You can learn more about this configuration option here.

from next.js.

Btw, it can be a pain with Auth. Using the next/prev btns can lead to still display a cached protected page after logout.

from next.js.

Member

thats cool, i will try it

from next.js.

Hi -- the behavior you're observing relates to the client router cache.

If you'd like to disable the client router cache so that every request hits the server, you can disable it by modifying your next.config.js as follows:

/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    staleTimes: {
      dynamic: 0,
    },
  },
}

module.exports = nextConfig

You can learn more about this configuration option here.

Already saw this, but it didn't resolve all my issues related to this "Lazy" middleware behavior. :/
Also, I tried to invalidate the client router cache, using a router.refresh call, which still didn't seem to fix my issue.

Maybe I will open an issue for that. /shrug

from next.js.

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

from next.js.