Handling different HTTP methods in Django - Step-by-Step Execution

Concept Flow - Handling different HTTP methods

Request arrives

↓

Check HTTP method

↓

Handle

↓

Send Response

↓

End

The server receives a request, checks its HTTP method, handles GET or POST accordingly, or returns an error for unsupported methods, then sends the response.

Execution Sample

Django

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')
    else:
        return HttpResponse('Method not allowed', status=405)

This Django view checks the HTTP method of the request and returns a different response for GET, POST, or other methods.

Execution Table

Step	Request Method	Condition Checked	Branch Taken	Response Content	Status Code
1	GET	request.method == 'GET'	True	This is a GET request	200
2	POST	request.method == 'GET'	False
3	POST	request.method == 'POST'	True	This is a POST request	200
4	PUT	request.method == 'GET'	False
5	PUT	request.method == 'POST'	False
6	PUT	else branch	True	Method not allowed	405

💡 Execution stops after returning the appropriate HttpResponse based on the request method.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 6
request.method	None	GET	POST	PUT
Response Content	None	This is a GET request	This is a POST request	Method not allowed
Status Code	None	200	200	405

Key Moments - 2 Insights

Why does the code check request.method multiple times instead of once?

Because each HTTP method needs a different response, the code checks request.method step-by-step to decide which branch to take, as shown in execution_table rows 1, 2-3, and 4-6.

What happens if the request method is neither GET nor POST?

The else branch runs, returning a 405 status code with 'Method not allowed', as seen in execution_table rows 4-6.

Visual Quiz - 3 Questions

Look at the execution table, what response content is returned when the request method is POST?

A This is a POST request

B This is a GET request

C Method not allowed

D No response

💡 Hint

Check the row where Request Method is POST and Branch Taken is True for request.method == 'POST'.

At which step does the condition request.method == 'GET' evaluate to False for a PUT request?

A Step 1

B Step 4

C Step 6

D Step 3

💡 Hint

Look at the execution_table row where Request Method is PUT and the first condition check.

If we add support for the DELETE method, how would the execution table change?

A Remove the POST condition

B Change the else branch to handle DELETE only

C Add a new condition checking for DELETE and a corresponding response row

D No changes needed

💡 Hint

Think about how GET and POST are handled separately in the execution_table.

Concept Snapshot

Django views check request.method to handle HTTP methods.
Use if-elif-else to respond differently to GET, POST, or others.
Return HttpResponse with content and status code.
Unsupported methods should return 405 status.
This keeps your app clear and user-friendly.

Full Transcript

In Django, when a request comes to a view, the code checks the HTTP method using request.method. If it is GET, the view returns a response for GET. If it is POST, it returns a response for POST. For any other method, it returns a 405 Method Not Allowed response. This flow ensures the server handles requests properly based on their method. The execution table shows step-by-step how the method is checked and which response is returned. Variables like request.method, response content, and status code change accordingly. Beginners often wonder why multiple checks are needed or what happens with unsupported methods. The quiz questions help reinforce understanding by referencing these steps. This approach keeps your Django views organized and responsive to different HTTP methods.

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