Request object properties in Flask - Step-by-Step Execution

Concept Flow - Request object properties

Client sends HTTP request

↓

Flask receives request

↓

Request object created

↓

Access properties: method, url, headers, args, form, json

↓

Use properties in route function

↓

Send response back to client

When Flask gets a request, it creates a Request object. You can then read its properties like method, URL, headers, and data to handle the request.

Execution Sample

Flask

from flask import Flask, request
app = Flask(__name__)

@app.route('/submit', methods=['GET', 'POST'])
def submit():
    return f"Method: {request.method}, URL: {request.url}"

This code shows how to read the HTTP method and URL from the Flask request object inside a route.

Execution Table

Step	Action	Request.method	Request.url	Output
1	Client sends GET request to /submit	GET	http://localhost/submit	None yet
2	Flask creates Request object	GET	http://localhost/submit	None yet
3	Route function runs, reads request.method and request.url	GET	http://localhost/submit	Method: GET, URL: http://localhost/submit
4	Response sent back with output string	GET	http://localhost/submit	Method: GET, URL: http://localhost/submit
5	Client receives response	GET	http://localhost/submit	Method: GET, URL: http://localhost/submit
6	Client sends POST request to /submit	POST	http://localhost/submit	None yet
7	Flask creates Request object	POST	http://localhost/submit	None yet
8	Route function runs, reads request.method and request.url	POST	http://localhost/submit	Method: POST, URL: http://localhost/submit
9	Response sent back with output string	POST	http://localhost/submit	Method: POST, URL: http://localhost/submit
10	Client receives response	POST	http://localhost/submit	Method: POST, URL: http://localhost/submit

💡 Execution stops after response is sent back to client.

Variable Tracker

Variable	Start	After Step 2	After Step 7	Final
request.method	None	GET	POST	POST
request.url	None	http://localhost/submit	http://localhost/submit	http://localhost/submit

Key Moments - 2 Insights

Why does request.method change between steps 2 and 7?

Because each HTTP request creates a new Request object with its own method property. Step 2 is for the GET request, step 7 is for the POST request.

Can request.url be different for the same route?

Yes, request.url includes the full URL including query parameters, so it can vary even if the route path is the same.

Visual Quiz - 3 Questions

Look at the execution table, what is the request.method at step 8?

A GET

B POST

C PUT

D DELETE

💡 Hint

Check the 'Request.method' column at step 8 in the execution_table.

At which step does Flask create the Request object for the POST request?

A Step 2

B Step 6

C Step 7

D Step 8

💡 Hint

Look for the step where 'Flask creates Request object' with method POST.

If the client sends a GET request with query parameters, which Request property holds them?

A request.args

B request.form

C request.json

D request.headers

💡 Hint

Query parameters are accessed via request.args in Flask.

Concept Snapshot

Flask creates a Request object for each HTTP request.
Use request.method to get HTTP method (GET, POST, etc).
Use request.url for full URL.
Use request.args for query parameters.
Use request.form for form data.
Use request.json for JSON body data.

Full Transcript

When a client sends an HTTP request to a Flask app, Flask creates a Request object representing that request. This object has properties like method, url, args, form, and json. The method tells you if the request is GET or POST. The url shows the full address requested. Query parameters are in args, form data in form, and JSON data in json. The route function can read these properties to decide how to respond. Each new request creates a new Request object with its own properties. This trace showed GET and POST requests to the same route, how Flask creates the Request object, and how the route reads method and url to build a response.

Practice

1. What does request.method in Flask represent?

easy

A. The client's IP address

B. The URL path requested by the client

C. The response status code

D. The HTTP method used by the client (GET, POST, etc.)

Solution

1. Step 1: Understand the role of request.method

   This property tells you which HTTP method the client used to send the request, such as GET or POST.

2. Step 2: Differentiate from other request properties

   It is not the URL path, IP address, or response code, which are accessed differently.

3. Final Answer:

   The HTTP method used by the client (GET, POST, etc.) -> Option D

4. Quick Check:

   request.method = HTTP method [OK]

Hint: Remember: method means GET, POST, PUT, DELETE [OK]

Common Mistakes:

• Confusing method with URL or path
• Thinking method is client IP
• Mixing method with response status

2. Which of the following is the correct way to access query parameters from a Flask request object?

easy

A. request.args.get('param')

B. request.form['param']

C. request.cookies['param']

D. request.headers['param']

Solution

1. Step 1: Identify how query parameters are accessed

   Query parameters are part of the URL after the question mark and are accessed via request.args.

2. Step 2: Use the correct method to get a parameter

   Using request.args.get('param') safely retrieves the value or returns None if missing.

3. Final Answer:

   request.args.get('param') -> Option A

4. Quick Check:

   Query params = request.args.get() [OK]

Hint: Query params use request.args.get('name') [OK]

Common Mistakes:

• Using request.form for query parameters
• Trying to get query params from cookies or headers
• Using request.args['param'] without .get() risking KeyError

3. Given this Flask route code snippet, what will be printed if a client sends a POST request with form data {'username': 'alice'}?

from flask import Flask, request
app = Flask(__name__)

@app.route('/login', methods=['POST'])
def login():
    user = request.form.get('username')
    method = request.method
    return f"User: {user}, Method: {method}"

medium

A. User: alice, Method: POST

B. User: None, Method: GET

C. User: alice, Method: GET

D. User: None, Method: POST

Solution

1. Step 1: Understand the request method and form data

   The client sends a POST request with form data containing 'username' = 'alice'.

2. Step 2: Check how data is accessed in the code

   The code uses request.form.get('username') which retrieves 'alice', and request.method which is 'POST'.

3. Final Answer:

   User: alice, Method: POST -> Option A

4. Quick Check:

   Form data and method match output [OK]

Hint: Form data is in request.form; method is request.method [OK]

Common Mistakes:

• Assuming method is GET when POST was sent
• Using request.args instead of request.form for POST data
• Expecting None for existing form data

4. What is wrong with this Flask code snippet if it raises a KeyError when accessing request.form['email']?

@app.route('/submit', methods=['POST'])
def submit():
    email = request.form['email']
    return f"Email: {email}"

medium

A. Flask requires request.args for form data

B. The route should accept GET method instead of POST

C. The form data might not include 'email', causing KeyError

D. request.form cannot be accessed directly

Solution

1. Step 1: Understand why KeyError occurs

   Accessing request.form['email'] raises KeyError if 'email' is missing in the form data.

2. Step 2: Suggest safer access method

   Use request.form.get('email') to avoid KeyError and get None if missing.

3. Final Answer:

   The form data might not include 'email', causing KeyError -> Option C

4. Quick Check:

   Missing key in form causes KeyError [OK]

Hint: Use .get() to avoid KeyError on missing form keys [OK]

Common Mistakes:

• Assuming form always has the key
• Confusing form data with query parameters
• Thinking request.form is inaccessible

5. You want to check if a client sent a cookie named session_id in a Flask route. Which code snippet correctly checks for it and returns its value or 'No session' if missing? A)

sid = request.cookies['session_id']
return sid if sid else 'No session'

B)

sid = request.cookies.get('session_id')
return sid or 'No session'

C)

sid = request.form.get('session_id')
return sid or 'No session'

D)

sid = request.args.get('session_id')
return sid or 'No session'

hard

A. Access cookie directly with [] and check truthiness

B. Use .get() on cookies and return fallback if missing

C. Check form data for cookie value

D. Check query parameters for cookie value

Solution

1. Step 1: Identify how to safely access cookies

   Cookies are accessed via request.cookies. Using .get() avoids KeyError if cookie is missing.

2. Step 2: Return cookie value or fallback

   Using sid or 'No session' returns the cookie value if present, else the fallback string.

3. Final Answer:

   Use .get() on cookies and return fallback if missing -> Option B

4. Quick Check:

   Cookies use request.cookies.get() safely [OK]

Hint: Use request.cookies.get('name') to avoid errors [OK]

Common Mistakes:

• Accessing cookies with [] risking KeyError
• Looking for cookies in form or args
• Not providing fallback for missing cookie