View decorators (require_GET, require_POST) in Django - Step-by-Step Execution

Concept Flow - View decorators (require_GET, require_POST)

HTTP Request Received

↓

Check HTTP Method

↓

Call View

↓

Return 405 Method Not Allowed

↓

Response

The decorator checks the HTTP method of the request. If it matches (GET or POST), it calls the view. Otherwise, it returns a 405 error.

Execution Sample

Django

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

This code only allows GET requests to reach the view; other methods get a 405 error.

Execution Table

Step	HTTP Method	Decorator Check	Action	Response
1	GET	require_GET passes	Call my_view	HttpResponse with 'Hello GET'
2	POST	require_GET fails	Return 405 Method Not Allowed	405 Error
3	GET	require_POST fails	Return 405 Method Not Allowed	405 Error
4	POST	require_POST passes	Call my_view	HttpResponse with 'Hello POST'

💡 Execution stops when the HTTP method does not match the decorator, returning 405 error.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
HTTP Method	None	GET	POST	GET	POST
Decorator Check Result	None	Pass	Fail	Fail	Pass
Response	None	'Hello GET'	405 Error	405 Error	'Hello POST'

Key Moments - 2 Insights

Why does a POST request get a 405 error when using @require_GET?

Because the decorator checks if the request method is GET. If not, it returns 405 as shown in execution_table row 2.

Can @require_POST allow GET requests to reach the view?

No, @require_POST only allows POST requests. GET requests cause a 405 error as shown in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution_table, what response does a GET request get with @require_GET?

A 405 Method Not Allowed

B HttpResponse with 'Hello GET'

C Redirect to another page

D Empty response

💡 Hint

Check execution_table row 1 under Response column.

At which step does the decorator return a 405 error for a POST request with @require_GET?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at execution_table row 2 where HTTP Method is POST and Decorator Check fails.

If you change @require_GET to @require_POST, what happens to GET requests?

A They get a 405 error

B They redirect to POST method

C They pass and call the view

D They get a 404 error

💡 Hint

See execution_table row 3 where GET with require_POST fails and returns 405.

Concept Snapshot

Use @require_GET or @require_POST to limit views to only GET or POST requests.
If the request method does not match, Django returns a 405 Method Not Allowed error.
This helps protect views from unwanted HTTP methods.
Syntax: @require_GET\ndef view(request): ...
Only requests with GET method reach the view function.

Full Transcript

View decorators like require_GET and require_POST check the HTTP method of incoming requests before calling the view function. If the method matches the decorator, the view runs and returns a response. If not, Django returns a 405 Method Not Allowed error. For example, @require_GET only allows GET requests. POST or other methods get blocked with 405. This protects views from handling unexpected methods. The execution table shows how requests with different methods are handled step-by-step. Variable tracking shows how the HTTP method and response change. Common confusions include why POST requests fail with @require_GET and vice versa. The visual quiz tests understanding of these behaviors. Overall, these decorators help control which HTTP methods your Django views accept.