Next.js from Development to Deployment - Persist Logged In User

The video tutorial explains how to persist user data by checking user login status using a custom API route. It involves creating a User API, handling cookies for authentication, and fetching user data from Strapi. The tutorial covers managing API responses, setting user state, and implementing a user login check with useEffect. Finally, it demonstrates creating a dashboard page and redirecting users post-login.

What is the purpose of creating a new API file in the context of user authentication?

• To store user passwords securely

• To manage user sessions

• To handle user login requests

• To retrieve user information using a token

Which HTTP method is used to fetch user data in the described implementation?

• GET

• DELETE

• PUT

• POST

What should be done if the cookie containing the token is not found?

• Log the user out

• Redirect to the login page

• Return a 403 Forbidden status

• Return a 200 OK status

How is the token extracted from the cookie in the implementation?

• By using a regular expression

• By calling a custom function

• By using the cookie package to parse it

• By manually splitting the cookie string

What happens if the Strapi API response indicates the user is forbidden?

• The user data is cached for later use

• The user is redirected to the home page

• A 403 status is returned with a 'user forbidden' message

• The user is logged out

What change occurs in the navigation bar when a user is logged in?

• It displays a logout button

• It shows a welcome message

• It switches to show links for logged-in users

• It hides all navigation links

What is the purpose of setting up a dashboard page in the authentication process?

• To manage user settings

• To redirect users after login

• To log user activities

• To display user statistics