301 and 302 redirects in Rest API - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a 301 redirect?

A 301 redirect is a permanent redirect from one URL to another. It tells browsers and search engines that the page has moved permanently.

beginner

What does a 302 redirect mean?

A 302 redirect is a temporary redirect. It tells browsers and search engines that the page has moved temporarily and may return to the original URL.

intermediate

When should you use a 301 redirect instead of a 302 redirect?

Use a 301 redirect when you want to permanently move a page and transfer SEO value. Use 302 if the move is temporary and you want to keep the original URL indexed.

intermediate

How do browsers handle 301 and 302 redirects differently?

Browsers cache 301 redirects because they are permanent, so they remember the new URL. 302 redirects are not cached as strongly because they are temporary.

beginner

What HTTP header is used to specify the new URL in a redirect?

The 'Location' header is used in the HTTP response to tell the browser the new URL to redirect to.

Which HTTP status code indicates a permanent redirect?

A 301

B 302

C 404

D 500

301 means permanent redirect, while 302 means temporary redirect.

What does a 302 redirect tell search engines?

A The page has moved temporarily

B The server has an error

C The page is not found

D The page has moved permanently

302 means the page is temporarily moved, so search engines keep the original URL indexed.

Which HTTP header contains the new URL in a redirect response?

A Content-Type

B Location

C Authorization

D Accept

The Location header tells the browser where to go next.

If you want to permanently move a page and keep SEO value, which redirect should you use?

A 302

B 404

C 301

D 200

301 is a permanent redirect and passes SEO value to the new URL.

How do browsers treat 301 redirects compared to 302 redirects?

A Do not cache either

B Cache 302 redirects, but not 301 redirects

C Cache both equally

D Cache 301 redirects, but not 302 redirects

Browsers cache 301 redirects because they are permanent, but treat 302 redirects as temporary and do not cache them strongly.

Explain the difference between a 301 and a 302 redirect and when to use each.

Think about whether the page move is permanent or temporary.

Describe how browsers handle caching for 301 and 302 redirects.

Consider the permanence of the redirect.

Practice

1. What does a 301 redirect indicate in a REST API?

easy

A. The resource has been deleted.

B. The resource is temporarily unavailable.

C. The resource has moved permanently to a new URL.

D. The resource requires authentication.

Solution

1. Step 1: Understand the meaning of 301 redirect

   A 301 redirect means the resource has moved permanently to a new location.

2. Step 2: Compare with other options

   Other options describe different HTTP statuses, not 301 redirect.

3. Final Answer:

   The resource has moved permanently to a new URL. -> Option C

4. Quick Check:

   301 redirect = permanent move [OK]

Hint: 301 means permanent move, 302 means temporary move [OK]

Common Mistakes:

• Confusing 301 with 302 redirect
• Thinking 301 means resource deleted
• Assuming 301 is for authentication

2. Which HTTP status code is used for a temporary redirect?

easy

A. 301

B. 302

C. 404

D. 500

Solution

1. Step 1: Identify status codes for redirects

   302 is the standard status code for temporary redirects.

2. Step 2: Eliminate other codes

   301 is permanent redirect, 404 is not found, 500 is server error.

3. Final Answer:

   302 -> Option B

4. Quick Check:

   Temporary redirect = 302 [OK]

Hint: 302 means temporary redirect, not 301 [OK]

Common Mistakes:

• Mixing 301 and 302 codes
• Choosing 404 or 500 by mistake
• Not knowing redirect codes

3. What will be the HTTP status code returned by this REST API snippet?

return Response(status=301, headers={'Location': 'https://newsite.com'})

medium

A. 301 Moved Permanently

B. 302 Found

C. 200 OK

D. 404 Not Found

Solution

1. Step 1: Analyze the status code in the response

   The code explicitly sets status=301, which means permanent redirect.

2. Step 2: Check the Location header

   The Location header points to the new URL, confirming redirect behavior.

3. Final Answer:

   301 Moved Permanently -> Option A

4. Quick Check:

   Status 301 with Location = permanent redirect [OK]

Hint: Status 301 with Location header means permanent redirect [OK]

Common Mistakes:

• Assuming 200 OK without checking status
• Confusing 301 with 302
• Ignoring Location header

4. Identify the error in this code snippet for a temporary redirect:

return Response(status=301, headers={'Location': 'https://temp.example.com'})

medium

A. Location header is missing.

B. Headers should not include Location.

C. Status code 301 is correct for temporary redirect.

D. Status code should be 302 for temporary redirect.

Solution

1. Step 1: Check status code for temporary redirect

   Temporary redirects require status code 302, not 301.

2. Step 2: Verify headers

   Location header is present and correct, so no error there.

3. Final Answer:

   Status code should be 302 for temporary redirect. -> Option D

4. Quick Check:

   Temporary redirect = 302, not 301 [OK]

Hint: Use 302 status for temporary redirects, not 301 [OK]

Common Mistakes:

• Using 301 instead of 302 for temporary redirects
• Omitting Location header
• Misunderstanding redirect status codes

5. You want to permanently redirect old API endpoints to new ones but keep temporary redirects for beta features. Which status codes should you use for each case?

hard

A. 301 for old endpoints, 302 for beta features

B. 302 for old endpoints, 301 for beta features

C. 404 for old endpoints, 302 for beta features

D. 500 for old endpoints, 301 for beta features

Solution

1. Step 1: Determine redirect type for old endpoints

   Old endpoints moved permanently, so use 301 status code.

2. Step 2: Determine redirect type for beta features

   Beta features are temporary, so use 302 status code.

3. Final Answer:

   301 for old endpoints, 302 for beta features -> Option A

4. Quick Check:

   Permanent = 301, Temporary = 302 [OK]

Hint: Permanent redirect = 301, temporary redirect = 302 [OK]

Common Mistakes:

• Swapping 301 and 302 codes
• Using error codes instead of redirects
• Not distinguishing permanent vs temporary