View decorators (require_GET, require_POST) in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the @require_GET decorator do in Django views?

The @require_GET decorator allows a Django view to accept only HTTP GET requests. If a different request method is used, Django returns a 405 Method Not Allowed response.

beginner

How does the @require_POST decorator affect a Django view?

The @require_POST decorator restricts a Django view to accept only HTTP POST requests. Requests with other methods get a 405 Method Not Allowed response.

intermediate

Why use @require_GET or @require_POST decorators in Django?

They help make views safer and clearer by ensuring only the intended HTTP methods are allowed, preventing accidental or malicious requests with wrong methods.

beginner

What HTTP status code does Django return if a request method is not allowed by @require_GET or @require_POST?

Django returns a 405 Method Not Allowed status code when the request method does not match the decorator's requirement.

intermediate

Can you combine @require_GET and @require_POST on the same Django view?

No, combining @require_GET and @require_POST on the same view doesn't make sense because they restrict to different HTTP methods. Use @require_http_methods if multiple methods are allowed.

What happens if a Django view decorated with @require_GET receives a POST request?

A The view processes the POST request normally.

B Django returns a 404 Not Found error.

C Django returns a 405 Method Not Allowed error.

D The request is redirected to a GET request.

The @require_GET decorator only allows GET requests. Other methods like POST get a 405 Method Not Allowed response.

Which decorator restricts a Django view to only accept POST requests?

A @require_GET

B @require_POST

C @require_http_methods(['GET', 'POST'])

D @allow_POST

@require_POST restricts the view to POST requests only.

If you want a Django view to accept both GET and POST requests, which decorator should you use?

A @require_http_methods(['GET', 'POST'])

B @require_POST

C @require_GET

D No decorator needed

@require_http_methods(['GET', 'POST']) allows multiple HTTP methods.

What HTTP status code indicates a method is not allowed on a Django view?

A 405

B 403

C 404

D 500

405 means Method Not Allowed, used when the HTTP method is blocked by decorators like @require_GET.

Which of these is a benefit of using @require_POST on a Django view?

A Allows any HTTP method

B Converts GET requests to POST

C Automatically logs user data

D Improves security by limiting request methods

Restricting to POST helps prevent unwanted or unsafe requests, improving security.

Explain how @require_GET and @require_POST decorators control access to Django views.

Think about what happens when a request uses the wrong method.

Describe a situation where you would use @require_POST in a Django application.

Consider when data changes happen in web apps.

Practice

1. What is the main purpose of the @require_GET decorator in Django views?

easy

A. To allow only GET requests to access the view

B. To allow only POST requests to access the view

C. To allow both GET and POST requests to access the view

D. To disable all HTTP requests to the view

Solution

1. Step 1: Understand the decorator's role

   The @require_GET decorator restricts the view to accept only GET requests.

2. Step 2: Compare with other decorators

   Unlike @require_POST which allows only POST, @require_GET is specific to GET requests.

3. Final Answer:

   To allow only GET requests to access the view -> Option A

4. Quick Check:

   @require_GET = allows GET only [OK]

Hint: Remember GET is for reading data, require_GET allows only that [OK]

Common Mistakes:

• Confusing @require_GET with @require_POST
• Thinking it allows all request types
• Assuming it disables the view

2. Which of the following is the correct way to import and use the @require_POST decorator in a Django view?

easy

A. from django.views.decorators import require_POST

@require_POST
def my_view(request):
pass

B. from django.views.decorators.http import require_GET

@require_POST
def my_view(request):
pass

C. from django.http import require_POST

@require_POST
def my_view(request):
pass

D. from django.views.decorators.http import require_POST

@require_POST
def my_view(request):
pass

Solution

1. Step 1: Identify the correct import path

   The @require_POST decorator is imported from django.views.decorators.http.

2. Step 2: Check usage syntax

   The decorator is applied directly above the view function with @require_POST.

3. Final Answer:

   from django.views.decorators.http import require_POST @require_POST def my_view(request): pass -> Option D

4. Quick Check:

   Correct import and decorator usage = from django.views.decorators.http import require_POST @require_POST def my_view(request): pass [OK]

Hint: Import from django.views.decorators.http for both decorators [OK]

Common Mistakes:

• Importing from wrong module like django.http
• Using @require_GET instead of @require_POST
• Missing the decorator above the function

3. Consider this Django view code snippet:

from django.views.decorators.http import require_GET
from django.http import HttpResponse

@require_GET
def sample_view(request):
    return HttpResponse('Hello GET')

What will happen if a POST request is sent to sample_view?

medium

A. The view will return 'Hello GET' response

B. The view will raise a 405 Method Not Allowed error

C. The view will ignore the POST and treat it as GET

D. The view will crash with a server error

Solution

1. Step 1: Understand @require_GET behavior

   The decorator allows only GET requests; other methods are blocked.

2. Step 2: Check response to disallowed methods

   When a POST request is sent, Django returns a 405 Method Not Allowed error automatically.

3. Final Answer:

   The view will raise a 405 Method Not Allowed error -> Option B

4. Quick Check:

   @require_GET blocks POST with 405 error [OK]

Hint: require_GET blocks non-GET with 405 error [OK]

Common Mistakes:

• Assuming POST is accepted and returns normal response
• Thinking it crashes the server
• Believing it silently converts POST to GET

4. You have this Django view:

from django.views.decorators.http import require_POST
from django.http import HttpResponse

@require_POST
def submit_data(request):
    return HttpResponse('Data submitted')

When testing, you accidentally send a GET request and get an error. What is the most likely cause?

medium

A. The @require_POST decorator blocks GET requests causing a 405 error

B. The HttpResponse is not imported correctly

C. The view is missing a return statement

D. The view function name is invalid

Solution

1. Step 1: Analyze decorator effect on request methods

   The @require_POST decorator allows only POST requests and blocks others.

2. Step 2: Understand error cause on GET request

   Sending a GET request triggers a 405 Method Not Allowed error because GET is disallowed.

3. Final Answer:

   The @require_POST decorator blocks GET requests causing a 405 error -> Option A

4. Quick Check:

   @require_POST blocks GET with 405 error [OK]

Hint: GET requests fail on @require_POST with 405 error [OK]

Common Mistakes:

• Thinking missing return causes error
• Assuming HttpResponse import issue
• Blaming function name for HTTP method errors

5. You want a Django view to accept only POST requests but also want to add a custom message when a GET request is made instead of the default 405 error. Which approach correctly combines @require_POST with custom handling?

hard

A. Manually check request.method inside the view and return custom response without @require_POST

B. Use @require_POST and add a try-except block inside the view to catch MethodNotAllowed

C. Use @require_POST and catch the 405 error globally in middleware

D. Use @require_GET instead and handle POST requests manually

Solution

1. Step 1: Understand @require_POST behavior

   The @require_POST decorator returns an HttpResponseNotAllowed (405) directly without calling the view or raising an exception.

2. Step 2: Combine with custom handling

   To customize the 405 response while using the decorator, implement middleware that checks response.status_code == 405 in process_response and returns a custom message.

3. Final Answer:

   Use @require_POST and catch the 405 error globally in middleware -> Option C

4. Quick Check:

   @require_POST + middleware process_response for custom 405 [OK]

Hint: Middleware process_response customizes decorator's 405 response [OK]

Common Mistakes:

• Manually checking method without decorator (doesn't combine)
• Try-except in view (view not executed)
• Using @require_GET when POST is needed