View decorators (require_GET, require_POST) in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a Django view uses @require_GET and receives a POST request?

Consider a Django view decorated with @require_GET. What is the behavior when this view receives a POST request?

Django

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

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

A The view returns 'Hello GET' regardless of the request method.

B The view processes the POST request as a GET request silently.

C The view raises a 405 Method Not Allowed error for the POST request.

D The view raises a 404 Not Found error for the POST request.

💡 Hint

Think about what HTTP status code means 'Method Not Allowed'.

The @require_GET decorator restricts the view to only accept GET requests. If a POST request is made, Django automatically returns a 405 Method Not Allowed response.

📝 Syntax

intermediate

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

Select the correct decorator to restrict a Django view to accept only POST requests.

A @require_POST

B @require_GET

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

D @require_safe

💡 Hint

Look for the decorator that explicitly mentions POST.

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

🔧 Debug

advanced

Why does this Django view raise a 404 error instead of 405 when using @require_POST?

Given the code below, why does the view return a 404 Not Found error instead of a 405 Method Not Allowed when accessed with GET?

Django

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

@require_POST
def my_view(request):
    return HttpResponse('Hello POST')

A Django always returns 404 for disallowed methods by default.

B The decorator is incorrectly imported, causing it to fail silently.

C The view is not decorated properly; it should be @require_GET instead.

D The URL pattern is missing, so Django returns 404 before the decorator runs.

💡 Hint

Think about what happens if the URL is not matched in Django.

If the URL pattern is missing or incorrect, Django never reaches the view or its decorators and returns a 404 error.

🧠 Conceptual

advanced

What is the difference between @require_GET and @require_safe decorators in Django?

Choose the option that best describes the difference between @require_GET and @require_safe decorators.

A @require_GET allows only GET requests; @require_safe allows GET, HEAD, and OPTIONS requests.

B @require_GET allows all safe methods; @require_safe allows only GET.

C @require_GET allows GET and POST; @require_safe allows only GET.

D @require_GET allows only POST; @require_safe allows GET and POST.

💡 Hint

HEAD requests are considered safe HTTP methods.

@require_GET restricts to GET requests only, while @require_safe allows GET, HEAD, and OPTIONS requests, since they are safe methods.

❓ state_output

expert

What is the HTTP status code returned by a Django view decorated with @require_http_methods(['POST', 'PUT']) when accessed with a DELETE request?

Given a Django view decorated with @require_http_methods(['POST', 'PUT']), what HTTP status code will the server respond with if the client sends a DELETE request?

Django

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

@require_http_methods(['POST', 'PUT'])
def my_view(request):
    return HttpResponse('Hello')

A 200 OK

B 405 Method Not Allowed

C 500 Internal Server Error

D 404 Not Found

💡 Hint

Think about what status code means the method is not allowed.

The decorator restricts allowed methods to POST and PUT. A DELETE request is not allowed, so Django returns 405 Method Not Allowed.