View decorators (require_GET, require_POST) in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the decorator that allows only GET requests.

Django

from django.views.decorators.http import [1]

Drag options to blanks, or click blank then click option'

Alogin_required

Brequire_POST

Crequire_GET

Dcsrf_exempt

Attempts:

3 left

💡 Hint

Common Mistakes

Using require_POST instead of require_GET

Importing unrelated decorators

The require_GET decorator restricts a view to only handle GET requests.

2fill in blank

medium

Complete the code to decorate the view so it only accepts POST requests.

Django

@[1]
def submit_form(request):
    return HttpResponse('Form submitted')

Drag options to blanks, or click blank then click option'

Arequire_POST

Brequire_GET

Ccsrf_exempt

Dlogin_required

Attempts:

3 left

💡 Hint

Common Mistakes

Using require_GET instead of require_POST

Forgetting to add the decorator

The require_POST decorator ensures the view only accepts POST requests.

3fill in blank

hard

Fix the error in the code by completing the decorator import correctly.

Django

from django.views.decorators.http import [1]

@require_GET
def show_data(request):
    return HttpResponse('Data shown')

Drag options to blanks, or click blank then click option'

ArequirePost

Brequire_post

CrequireGet

Drequire_GET

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or camelCase names

Misspelling the decorator name

The correct decorator name is require_GET with uppercase GET.

4fill in blank

hard

Fill both blanks to create a view that only accepts GET requests and returns a simple response.

Django

from django.http import HttpResponse
from django.views.decorators.http import [1]

@[2]
def home(request):
    return HttpResponse('Welcome!')

Drag options to blanks, or click blank then click option'

Arequire_GET

Brequire_POST

Ccsrf_exempt

Dlogin_required

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing require_POST with require_GET

Forgetting to import the decorator

Import and use require_GET decorator to restrict the view to GET requests.

5fill in blank

hard

Fill all three blanks to create a POST-only view that returns a confirmation message.

Django

from django.http import HttpResponse
from django.views.decorators.http import [1]

@[2]
def submit(request):
    if request.method == '[3]':
        return HttpResponse('Submitted successfully')

Drag options to blanks, or click blank then click option'

Arequire_GET

Brequire_POST

CPOST

DGET

Attempts:

3 left

💡 Hint

Common Mistakes

Using require_GET decorator with POST method

Checking for wrong HTTP method string

Use require_POST decorator and check for 'POST' method string to restrict the view properly.

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