Handling different HTTP methods in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of handling different HTTP methods in a Django view?

Handling different HTTP methods allows a Django view to respond differently to requests like GET, POST, PUT, or DELETE, enabling the server to perform actions like showing data, submitting forms, updating, or deleting resources.

beginner

How do you check the HTTP method of a request in a Django view function?

You check the HTTP method by accessing request.method, which returns a string like 'GET' or 'POST'. You can then use if-else statements to handle each method accordingly.

intermediate

What Django class-based view method handles GET requests?

The get() method handles GET requests in class-based views. You define it to specify what happens when the server receives a GET request.

intermediate

How can you restrict a Django view to only accept POST requests?

You can use the @require_POST decorator from django.views.decorators.http to make sure the view only accepts POST requests. If another method is used, Django returns a 405 Method Not Allowed response.

intermediate

What is the difference between handling HTTP methods in function-based views and class-based views in Django?

In function-based views, you check request.method inside the function and write if-else logic. In class-based views, you define separate methods like get(), post(), etc., for each HTTP method, making the code cleaner and organized.

Which attribute do you use to check the HTTP method in a Django request?

A request.method

B request.type

C request.http_method

D request.action

The correct attribute is request.method, which returns the HTTP method as a string.

What HTTP method is typically used to submit form data to the server?

A GET

B POST

C DELETE

D PUT

POST is used to send data to the server, such as submitting form data.

In a Django class-based view, which method handles a POST request?

A get()

B handle_post()

C process_post()

D post()

The post() method handles POST requests in class-based views.

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

A @require_POST

B @require_http_methods(['POST'])

C @require_GET

D @only_post

The @require_POST decorator restricts the view to POST requests only.

What response does Django return if a view receives an unsupported HTTP method?

A 404 Not Found

B 500 Internal Server Error

C 405 Method Not Allowed

D 403 Forbidden

Django returns a 405 Method Not Allowed response when the HTTP method is not supported by the view.

Explain how to handle GET and POST requests differently in a Django function-based view.

Think about how you decide what to do based on request.method.

Describe how class-based views in Django organize code for different HTTP methods.

Consider how methods inside a class correspond to HTTP verbs.

Practice

1. In Django, which attribute of the request object helps you determine if the HTTP method is GET or POST inside a view?

easy

A. request.method

B. request.type

C. request.http_method

D. request.action

Solution

1. Step 1: Understand the request object in Django views

   The request object contains details about the HTTP request, including the method used.

2. Step 2: Identify the correct attribute for HTTP method

   The attribute request.method holds the HTTP method as a string like 'GET' or 'POST'.

3. Final Answer:

   request.method -> Option A

4. Quick Check:

   Check HTTP method with request.method [OK]

Hint: Use request.method to check HTTP method type [OK]

Common Mistakes:

• Using request.type instead of request.method
• Trying to access request.http_method which doesn't exist
• Confusing request.action with HTTP method

2. Which of the following is the correct way to restrict a Django view to only accept GET and POST requests using a decorator?

easy

A. @http_methods_only(["GET", "POST"])

B. @allow_methods("GET", "POST")

C. @accept_methods(["GET", "POST"])

D. @require_http_methods(["GET", "POST"])

Solution

1. Step 1: Recall Django's built-in decorators for HTTP methods

   Django provides @require_http_methods to restrict allowed HTTP methods on views.

2. Step 2: Check correct syntax for the decorator

   The decorator takes a list of allowed methods as strings, e.g., ["GET", "POST"].

3. Final Answer:

   @require_http_methods(["GET", "POST"]) -> Option D

4. Quick Check:

   Use @require_http_methods([...]) to restrict methods [OK]

Hint: Use @require_http_methods([...]) to limit HTTP methods [OK]

Common Mistakes:

• Using non-existent decorators like @allow_methods
• Passing methods as separate arguments instead of a list
• Misspelling the decorator name

3. What will be the output of the following Django view when accessed with a POST request?

from django.http import HttpResponse

def my_view(request):
    if request.method == 'GET':
        return HttpResponse('This is a GET request')
    elif request.method == 'POST':
        return HttpResponse('This is a POST request')

medium

A. This is a GET request

B. This is a POST request

C. Error: Method not allowed

D. No response returned

Solution

1. Step 1: Analyze the request method check

   The view checks if request.method is 'GET' or 'POST' and returns corresponding responses.

2. Step 2: Determine response for POST request

   Since the request is POST, the view returns 'This is a POST request' wrapped in an HttpResponse.

3. Final Answer:

   This is a POST request -> Option B

4. Quick Check:

   POST request returns 'This is a POST request' [OK]

Hint: Match request.method to response text [OK]

Common Mistakes:

• Assuming GET response for POST requests
• Expecting an error without decorator
• Missing return statement for POST branch

4. Identify the error in this Django view that tries to handle GET and POST methods:

def example_view(request):
    if request.method = 'GET':
        return HttpResponse('GET request')
    elif request.method == 'POST':
        return HttpResponse('POST request')

medium

A. Using single equals (=) instead of double equals (==) in the if condition

B. Missing import of HttpResponse

C. No return statement for other methods

D. Using elif instead of else

Solution

1. Step 1: Check the if condition syntax

   The condition uses request.method = 'GET' which is an assignment, not a comparison.

2. Step 2: Correct the comparison operator

   It should use == to compare values, like request.method == 'GET'.

3. Final Answer:

   Using single equals (=) instead of double equals (==) in the if condition -> Option A

4. Quick Check:

   Use == for comparison, not = [OK]

Hint: Use == to compare, not = [OK]

Common Mistakes:

• Confusing assignment (=) with comparison (==)
• Forgetting to import HttpResponse (though not asked here)
• Assuming elif must be else

5. You want a Django view to accept only POST requests and return a 405 error for others. Which is the best way to implement this behavior?

hard

A. Check request.method inside the view and return 405 manually

B. Use @csrf_exempt decorator to allow POST only

C. Use @require_http_methods(["POST"]) decorator on the view

D. Raise Http404 if method is not POST

Solution

1. Step 1: Understand Django's method restriction decorators

   The @require_http_methods decorator automatically restricts allowed HTTP methods and returns 405 if not allowed.

2. Step 2: Compare manual checking vs decorator

   While manual checking is possible, the decorator is cleaner, less error-prone, and standard practice.

3. Step 3: Evaluate other options

   @csrf_exempt is unrelated to method restriction; raising Http404 is incorrect for method errors.

4. Final Answer:

   Use @require_http_methods(["POST"]) decorator on the view -> Option C

5. Quick Check:

   Use @require_http_methods to restrict methods cleanly [OK]

Hint: Use @require_http_methods(["POST"]) to restrict POST only [OK]

Common Mistakes:

• Using @csrf_exempt to control HTTP methods
• Raising Http404 instead of 405 for wrong methods
• Manually coding method checks instead of decorator