Why views handle request logic in Django - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do Django views handle request logic?

In Django, views are responsible for processing incoming HTTP requests. Why is it important that views handle this request logic?

A Because views store the database models and handle data migrations automatically.

B Because views manage the server configuration and deployment settings.

C Because views are used to style the HTML pages with CSS and JavaScript.

D Because views connect the URL requested by the user to the code that processes data and returns a response.

💡 Hint

Think about what happens when a user visits a web page and how Django decides what to show.

Views in Django act as the middleman between the user's request and the data or template that should be shown. They contain the logic to process the request and return the right response.

❓ component_behavior

intermediate

What happens when a Django view receives a request?

Consider a Django view function that receives a GET request. What is the typical behavior of this view?

Django

from django.http import HttpResponse, HttpResponseNotAllowed

def example_view(request):
    if request.method == 'GET':
        return HttpResponse('Hello, world!')
    else:
        return HttpResponseNotAllowed(['GET'])

A It redirects the user to another website without processing the request.

B It automatically updates the database with new data from the request.

C It checks the request method, processes the GET request, and returns a response with content 'Hello, world!'.

D It ignores the request method and always returns an error.

💡 Hint

Look at how the view checks the request method and what it returns.

The view checks if the request method is GET, then returns a simple HTTP response. If the method is not GET, it returns a 'method not allowed' response.

❓ state_output

advanced

What is the output of this Django view when receiving a POST request?

Given the following Django view, what will be the HTTP response content if the request method is POST?

Django

from django.http import HttpResponse, HttpResponseNotAllowed

def my_view(request):
    if request.method == 'GET':
        return HttpResponse('GET request received')
    elif request.method == 'POST':
        return HttpResponse('POST request received')
    else:
        return HttpResponseNotAllowed(['GET', 'POST'])

A 'POST request received'

B Empty response with status 200

C HttpResponseNotAllowed error

D 'GET request received'

💡 Hint

Check the condition that matches the POST method.

The view returns 'POST request received' when the request method is POST, as per the elif branch.

📝 Syntax

advanced

Identify the syntax error in this Django view function

Which option contains a syntax error in the Django view function below?

Django

from django.http import HttpResponse

def sample_view(request):
    if request.method == 'GET':
        return HttpResponse('Hello')
    else:
        return HttpResponse('Other method')

A Missing colon after the if statement condition.

B HttpResponse is not imported.

C Indentation error in the else block.

D Using single quotes instead of double quotes in strings.

💡 Hint

Look carefully at the if statement syntax.

The if statement is missing a colon at the end of the condition line, which causes a syntax error.

🔧 Debug

expert

Why does this Django view raise an error when handling a request?

Examine the Django view below. When a request is made, it raises an error. What is the cause?

Django

from django.http import HttpResponse

def error_view(request):
    if request.method == 'POST':
        data = request.POST['username']
    return HttpResponse(f'User: {data}')

A The view does not handle GET requests, causing a 404 error.

B Variable 'data' is used outside the if block without guarantee it is assigned.

C HttpResponse is not imported, causing a NameError.

D request.POST does not contain 'username' key, causing a KeyError.

💡 Hint

Consider what happens if the request method is not POST.

If the request method is not POST, the variable 'data' is never assigned, but the return statement tries to use it, causing an UnboundLocalError.

Practice

1. Why do Django views handle request logic instead of templates?

easy

A. Because templates are only for styling the page

B. Because views process data and decide what response to send

C. Because views store the database records

D. Because templates handle user authentication

Solution

1. Step 1: Understand the role of views

   Views receive the user's request and decide what to do with it, like fetching data or processing input.

2. Step 2: Understand the role of templates

   Templates only display the data and do not contain logic to process requests.

3. Final Answer:

   Because views process data and decide what response to send -> Option B

4. Quick Check:

   Views handle logic [OK]

Hint: Remember: views handle logic, templates handle display [OK]

Common Mistakes:

• Thinking templates handle data processing
• Confusing views with database models
• Believing templates manage user authentication

2. Which of the following is the correct way to define a Django view function that handles a request?

easy

A. def my_view(request, response): return 'Hello'

B. def my_view(): return HttpResponse('Hello')

C. def my_view(request): print('Hello')

D. def my_view(request): return HttpResponse('Hello')

Solution

1. Step 1: Check function parameters

   A Django view must accept at least one parameter named 'request' representing the user's request.

2. Step 2: Check return type

   The view should return an HttpResponse object or similar, not just print or return a string.

3. Final Answer:

   def my_view(request): return HttpResponse('Hello') -> Option D

4. Quick Check:

   View(request) returns HttpResponse [OK]

Hint: View functions always take 'request' and return HttpResponse [OK]

Common Mistakes:

• Omitting the request parameter
• Returning plain strings instead of HttpResponse
• Adding extra parameters not handled by Django

3. Given this view code:

from django.http import HttpResponse

def greet(request):
    name = request.GET.get('name', 'Guest')
    return HttpResponse(f'Hello, {name}!')

What will be the response if the user visits /greet?name=Anna?

medium

A. Hello, Anna!

B. Hello, Guest!

C. Hello, None!

D. Error: name parameter missing

Solution

1. Step 1: Understand request.GET.get usage

   The code tries to get the 'name' parameter from the URL query string; if missing, it uses 'Guest'.

2. Step 2: Check the URL query parameter

   The URL has '?name=Anna', so 'name' is 'Anna', not missing.

3. Final Answer:

   Hello, Anna! -> Option A

4. Quick Check:

   Query param 'name' = Anna [OK]

Hint: Check URL query parameters and default values [OK]

Common Mistakes:

• Assuming default is always used
• Confusing GET with POST data
• Expecting an error if parameter is missing

4. This view code has an error:

def show(request):
    user = request.POST['username']
    return HttpResponse(f'User: {user}')

What is the likely error when a GET request is made to this view?

medium

A. KeyError because 'username' is missing in POST data

B. SyntaxError due to missing colon

C. TypeError because request.POST is not a dictionary

D. No error, returns empty user

Solution

1. Step 1: Understand request.POST usage

   request.POST contains data only for POST requests; a GET request has no POST data.

2. Step 2: Accessing missing key causes error

   Accessing request.POST['username'] when missing raises KeyError.

3. Final Answer:

   KeyError because 'username' is missing in POST data -> Option A

4. Quick Check:

   Missing POST key causes KeyError [OK]

Hint: Access POST keys safely or check request method first [OK]

Common Mistakes:

• Assuming POST data exists on GET requests
• Expecting empty string instead of error
• Confusing KeyError with SyntaxError

5. You want a view to handle both GET and POST requests differently. Which code correctly handles this logic?

hard

A. def my_view(request):
if request.GET:
return HttpResponse('Posted')
else:
return HttpResponse('Got')

B. def my_view(request):
if request.POST:
return HttpResponse('Posted')
else:
return HttpResponse('Got')

C. def my_view(request):
if request.method == 'POST':
return HttpResponse('Posted')
else:
return HttpResponse('Got')

D. def my_view(request):
if request.method == 'GET':
return HttpResponse('Posted')
else:
return HttpResponse('Got')

Solution

1. Step 1: Check how to detect request method

   Use request.method to check if the request is 'POST' or 'GET'.

2. Step 2: Verify correct branching

   def my_view(request): if request.method == 'POST': return HttpResponse('Posted') else: return HttpResponse('Got') correctly returns 'Posted' for POST and 'Got' for others (like GET).

3. Final Answer:

   def my_view(request): if request.method == 'POST': return HttpResponse('Posted') else: return HttpResponse('Got') -> Option C

4. Quick Check:

   Use request.method to branch logic [OK]

Hint: Check request.method string, not request.POST or GET dict [OK]

Common Mistakes:

• Checking if request.POST or request.GET is truthy instead of method
• Mixing up GET and POST conditions
• Returning wrong response for request types