401 Unauthorized vs 403 Forbidden in Rest API - Visual Side-by-Side Comparison

Concept Flow - 401 Unauthorized vs 403 Forbidden

Client sends request

↓

Server checks authentication

↓

Respond 401 Unauthorized

↓

Server checks authorization

↓

Respond 403 Forbidden

↓

Respond 200 OK or other success

↓

End

The server first checks if the client is authenticated (logged in). If not, it sends 401 Unauthorized. If authenticated but not allowed to access, it sends 403 Forbidden.

Execution Sample

Rest API

GET /profile HTTP/1.1
Host: example.com
Authorization: Bearer invalid_token

Response: 401 Unauthorized

Client sends a request with invalid token, server responds with 401 Unauthorized because authentication failed.

Execution Table

Step	Check	Condition	Result	Server Response
1	Check authentication token	Token valid?	No	401 Unauthorized
2	Check authorization	Skipped because not authenticated	-	-
3	End	Request denied	-	-

💡 Authentication failed at step 1, so server returns 401 Unauthorized and stops.

Variable Tracker

Variable	Start	After Step 1	After Step 2	Final
authentication	unknown	failed	failed	failed
authorization	unknown	not checked	not checked	not checked
response_code	none	401	401	401

Key Moments - 2 Insights

Why does the server return 401 Unauthorized instead of 403 Forbidden when the token is invalid?

Because the client is not authenticated yet, the server stops at step 1 (see execution_table row 1) and returns 401 Unauthorized. Authorization is only checked after successful authentication.

When does the server return 403 Forbidden?

The server returns 403 Forbidden only if the client is authenticated (passed step 1) but does not have permission to access the resource (step 2). This is not shown in this trace but would happen after authentication succeeds.

Visual Quiz - 3 Questions

Look at the execution_table, what is the server response at step 1?

A 403 Forbidden

B 401 Unauthorized

C 200 OK

D 500 Internal Server Error

💡 Hint

Check the 'Server Response' column in execution_table row 1.

According to variable_tracker, what is the value of 'authorization' after step 1?

A not checked

B failed

C passed

D unknown

💡 Hint

Look at the 'authorization' row and 'After Step 1' column in variable_tracker.

If the client had a valid token but no permission, what response code would you expect?

A 401 Unauthorized

B 200 OK

C 403 Forbidden

D 404 Not Found

💡 Hint

Remember the flow: authentication first, then authorization. 403 means authenticated but forbidden.

Concept Snapshot

401 Unauthorized means you are not logged in or your credentials are missing/invalid.
403 Forbidden means you are logged in but do not have permission to access the resource.
Server checks authentication first, then authorization.
401 stops the request early; 403 means access denied despite authentication.
Use 401 to ask client to login, 403 to deny access after login.

Full Transcript

When a client sends a request to a server, the server first checks if the client is authenticated. If the client is not authenticated, the server responds with 401 Unauthorized, meaning the client must provide valid credentials. If the client is authenticated but does not have permission to access the requested resource, the server responds with 403 Forbidden. This means the client is recognized but not allowed to proceed. The execution flow shows that authentication is checked first, and if it fails, the server stops and returns 401. Authorization is only checked if authentication succeeds. Variables like authentication status and response code change accordingly during these steps. Understanding this helps developers correctly handle access control in APIs.

Practice

1. What does the HTTP status code 401 Unauthorized indicate in a REST API?

easy

A. The client is not authenticated or provided invalid credentials.

B. The client is authenticated but does not have permission to access the resource.

C. The requested resource was not found on the server.

D. The server encountered an internal error while processing the request.

Solution

1. Step 1: Understand the meaning of 401 Unauthorized

   The 401 status code means the client must authenticate itself to get the requested response. It usually means no or bad login info.

2. Step 2: Differentiate from 403 Forbidden

   403 means the client is authenticated but lacks permission. 401 means no valid authentication.

3. Final Answer:

   The client is not authenticated or provided invalid credentials. -> Option A

4. Quick Check:

   401 Unauthorized = No or bad login info [OK]

Hint: 401 means login problem; 403 means no permission [OK]

Common Mistakes:

• Confusing 401 with 403
• Thinking 401 means resource missing
• Assuming 401 means server error

2. Which HTTP status code should a REST API return when a user is logged in but tries to access a resource they don't have rights for?

easy

A. 404 Not Found

B. 401 Unauthorized

C. 403 Forbidden

D. 500 Internal Server Error

Solution

1. Step 1: Identify the meaning of 403 Forbidden

   403 means the user is authenticated but does not have permission to access the resource.

2. Step 2: Confirm 401 is for unauthenticated users

   401 is for users who are not logged in or have invalid credentials, so it does not apply here.

3. Final Answer:

   403 Forbidden -> Option C

4. Quick Check:

   403 Forbidden = Logged in but no permission [OK]

Hint: 403 means permission denied after login [OK]

Common Mistakes:

• Using 401 when user is logged in
• Confusing 403 with 404 Not Found
• Thinking 403 means server error

3. Consider this REST API response scenario:

{"status":401,"message":"Invalid token"}

What does this response tell the client?

medium

A. The client provided an invalid or missing authentication token.

B. The server failed to process the request due to an error.

C. The requested resource does not exist.

D. The client is authenticated but forbidden to access the resource.

Solution

1. Step 1: Analyze the status code 401

   401 means unauthorized, so the client is not properly authenticated.

2. Step 2: Interpret the message "Invalid token"

   This indicates the authentication token is missing or invalid, so the client must provide valid credentials.

3. Final Answer:

   The client provided an invalid or missing authentication token. -> Option A

4. Quick Check:

   401 + "Invalid token" = Bad login info [OK]

Hint: 401 with token error means bad or missing login [OK]

Common Mistakes:

• Thinking 401 means permission denied
• Assuming resource is missing
• Confusing 401 with server error

4. You have this REST API code snippet:

if (!user.isLoggedIn()) {
  return 403;
} else if (!user.hasAccess()) {
  return 401;
}

What is wrong with this code?

medium

A. It returns 401 when user lacks access, should be 403 instead.

B. The code is correct as is.

C. It should return 404 for unauthorized access.

D. It returns 403 when user is not logged in, should be 401 instead.

Solution

1. Step 1: Check the meaning of 401 and 403

   401 means unauthorized (not logged in), 403 means forbidden (no permission).

2. Step 2: Analyze the code logic

   The code returns 403 when user is not logged in, which is incorrect. It should return 401 here. It returns 401 when user lacks access, which should be 403.

3. Final Answer:

   It returns 403 when user is not logged in, should be 401 instead. -> Option D

4. Quick Check:

   Not logged in = 401, no permission = 403 [OK]

Hint: 401 for no login, 403 for no permission [OK]

Common Mistakes:

• Swapping 401 and 403 codes
• Using 404 for unauthorized
• Assuming code is correct without checking status meanings

5. You are designing a REST API for a file storage service. A user tries to access a file:

GET /files/123

The user is logged in but does not own the file. Which status code should your API return and why?

hard

A. 401 Unauthorized, because the user must re-authenticate to access the file.

B. 403 Forbidden, because the user is authenticated but not allowed to access this file.

C. 404 Not Found, to hide the existence of the file from unauthorized users.

D. 500 Internal Server Error, because the server cannot process the request.

Solution

1. Step 1: Determine user's authentication and ownership

   The user is logged in (authenticated) but does not own the file, so lacks permission.

2. Step 2: Choose correct status code for permission denial

   403 Forbidden is the correct code when the user is authenticated but not allowed to access the resource.

3. Final Answer:

   403 Forbidden, because the user is authenticated but not allowed to access this file. -> Option B

4. Quick Check:

   Logged in + no permission = 403 Forbidden [OK]

Hint: Logged in but no access? Return 403 Forbidden [OK]

Common Mistakes:

• Using 401 when user is logged in
• Using 404 to hide resource instead of 403
• Confusing 500 error with permission issues