Router cache does not revalidate about next.js

[icyJoseph]

Is the issue here that you redirect with a 301? I haven't had time to run your app, but here:

    if (isProtectedRoute && !isException) {
      const newUrl = new URL(`/auth/signin?path=${pathname}`, request.url);
      return NextResponse.redirect(newUrl, { status: 301 });
    }

If you have an unauthenticated user, and the route is protected, and not an excepted route, then you do a 301 to signin, and the browser saves those. Could you try using 302 instead? First clear your browser cache though, since those 301's are saved by it. https://fabricdigital.co.nz/blog/how-to-hard-refresh-your-browser-and-clear-cache

[Saman-Safaei-Dev]

The issue is resolved with this solution. I thought it's a bug. Thanks for your solution.

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[icyJoseph]

Nice, could you close the issue then? :)

[github-actions]

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.