The `redirect` function sends a temporary redirect (HTTP 307), suitable for temporary state changes, such as redirecting an unauthenticated user to the login page.

Question

You are working on an app, which implements a redirection functionality based on the user's role. The application has an app folder structure with a`dashboard` folder for authenticated users. You have a`route.js` file in`app/dashboard` that handles the redirection logic based on the user role.

```
import{ redirect, permanentRedirect } from 'next/navigation';

export async function route({ session }){
  if(!session || !session.user){
    return redirect('/login');
  }

if(session.user.role !== 'admin'){
    return permanentRedirect('/unauthorized');
  }

// Continue with rendering the dashboard for the admin
//...
}

// In this context,`session` is an object containing the user's session information.
```

Regarding the above scenario and code, what statement(s) is/are correct about handling redirects in Next.js with the App Router?

Accepted Answer

The`redirect` function sends a temporary redirect(HTTP 307), suitable for temporary state changes, such as redirecting an unauthenticated user to the login page.

Answer

The`redirect` and`permanentRedirect` functions can only be used in page components and not in`route.js` files.

Answer

Checking the`session` object and redirecting based on user role should be done client-side in a`useEffect`.

Answer

Using`permanentRedirect` to redirect non-admin users to a`/unauthorized` page is not possible in the App Router and requires custom middleware.

Question from the Next.js test

The `redirect` function sends a temporary redirect (HTTP 307), suitable for temporary state changes, such as redirecting an unauthenticated user to the login page.