HttpRequest object in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to access the HTTP method from the request object.

Django

method = request.[1]

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

Amethod

Bmethod()

CMETHOD

Dmethod_type

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses like a method call (e.g., request.method())

Using uppercase attribute names

Guessing attribute names that don't exist

The HttpRequest object has a method attribute that stores the HTTP method as a string, like 'GET' or 'POST'.

2fill in blank

medium

Complete the code to get the value of a GET parameter named 'page' from the request.

Django

page_number = request.GET.[1]('page', '1')

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

Afetch

Bget

Cretrieve

Dfind

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods like fetch or find which are not valid

Accessing parameters directly without a default, risking errors

The GET attribute is a dictionary-like object. Use its get method to safely access parameters with a default value.

3fill in blank

hard

Fix the error in accessing the POST data for a key 'username'.

Django

username = request.POST.[1]('username')

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

Aretrieve

Bpost

Cget

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to call post on request.POST

Using methods that don't exist on QueryDict objects

The POST attribute is a dictionary-like object. Use get to safely access keys.

4fill in blank

hard

Fill both blanks to check if the request is a POST and get the 'email' parameter safely.

Django

if request.[1] == 'POST':
    email = request.POST.[2]('email', '')

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

Amethod

Bget

Cpost

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using request.post instead of request.method

Using non-existent methods like fetch on POST data

Use request.method to check the HTTP method. Use get on request.POST to safely get parameters.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that maps each GET parameter key to its first value if the value length is greater than 3.

Django

filtered_params = {k: v[0] for k, v in request.GET.lists() if len([1]) [2] [3]

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

Av[0]

B>

C3

Dk

Attempts:

3 left

💡 Hint

Common Mistakes

Checking length of the key instead of the value

Using wrong comparison operators

Using the whole list instead of the first value

We check the length of the first value v[0] for each key-value pair. The condition uses the greater than operator and the number 3.

Practice

1. What does the HttpRequest object in Django primarily represent?

easy

A. The database connection settings

B. Information about the user's web request

C. The HTML template to render

D. The server's response to the user

Solution

1. Step 1: Understand the role of HttpRequest

   The HttpRequest object contains all details sent by the user when they visit a web page or submit a form.

2. Step 2: Differentiate from other components

   It is not about database settings, templates, or responses but about the incoming request data.

3. Final Answer:

   Information about the user's web request -> Option B

4. Quick Check:

   HttpRequest = user request info [OK]

Hint: HttpRequest always holds data sent by the user [OK]

Common Mistakes:

• Confusing HttpRequest with HttpResponse
• Thinking it holds database or template info
• Assuming it represents server settings

2. Which of the following is the correct way to access GET parameters from a Django HttpRequest object named request?

easy

A. request.GET['param']

B. request.POST['param']

C. request.params['param']

D. request.data['param']

Solution

1. Step 1: Identify how to access GET data

   In Django, GET parameters are accessed via the GET dictionary attribute of the HttpRequest object.

2. Step 2: Confirm the correct syntax

   Using request.GET['param'] retrieves the value of 'param' from the URL query string.

3. Final Answer:

   request.GET['param'] -> Option A

4. Quick Check:

   GET params use request.GET [OK]

Hint: Use request.GET for URL query parameters [OK]

Common Mistakes:

• Using request.POST for GET parameters
• Using non-existent attributes like request.params
• Confusing request.data with Django HttpRequest

3. Given the following Django view code, what will be printed if the URL is /search/?q=django?

def search_view(request):
    query = request.GET.get('q', 'none')
    print(query)
    return HttpResponse('Done')

medium

A. none

B. q

C. django

D. Error

Solution

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

   The method request.GET.get('q', 'none') tries to get the value of 'q' from the URL query string; if missing, returns 'none'.

2. Step 2: Analyze the URL query string

   The URL has ?q=django, so 'q' exists with value 'django'.

3. Final Answer:

   django -> Option C

4. Quick Check:

   GET param 'q' = 'django' [OK]

Hint: request.GET.get returns value or default if missing [OK]

Common Mistakes:

• Assuming .get returns the key name instead of value
• Confusing default value usage
• Expecting an error if key exists

4. Identify the error in this Django view code snippet:

def my_view(request):
    username = request.POST.get('username')
    if username:
        return HttpResponse(f"Hello, {username}!")
    else:
        return HttpResponse("No username provided")

medium

A. Missing import of HttpResponse

B. Using request.POST.get instead of request.GET.get

C. No error, code is correct

D. Incorrect use of f-string in HttpResponse

Solution

1. Step 1: Check for necessary imports

   The code uses HttpResponse but does not show an import statement for it, which is required.

2. Step 2: Verify usage of request.POST.get and f-string

   Using request.POST.get is valid for POST data, and f-string usage is correct in Python 3.6+.

3. Final Answer:

   Missing import of HttpResponse -> Option A

4. Quick Check:

   HttpResponse must be imported [OK]

Hint: Always import HttpResponse before using it [OK]

Common Mistakes:

• Assuming request.POST.get is wrong for POST data
• Thinking f-string is invalid syntax
• Ignoring missing imports causing runtime errors

5. You want to check if a user sent a custom header named X-Auth-Token in a Django view. Which is the correct way to access this header from the HttpRequest object named request?

hard

A. request.headers['X-Auth-Token']

B. request.POST['X-Auth-Token']

C. request.GET['X-Auth-Token']

D. request.META['HTTP_X_AUTH_TOKEN']

Solution

1. Step 1: Understand how Django stores HTTP headers

   Django stores HTTP headers in the request.META dictionary, with header names uppercased, prefixed by 'HTTP_', and dashes replaced by underscores.

2. Step 2: Convert 'X-Auth-Token' to META key

   The header X-Auth-Token becomes HTTP_X_AUTH_TOKEN in request.META.

3. Final Answer:

   request.META['HTTP_X_AUTH_TOKEN'] -> Option D

4. Quick Check:

   Custom headers use request.META with HTTP_ prefix [OK]

Hint: Custom headers in request.META with HTTP_ prefix [OK]

Common Mistakes:

• Using request.headers (added in Django 2.2 but not always reliable)
• Trying to get headers from GET or POST dictionaries
• Not converting header name to uppercase with HTTP_ prefix