After_request hooks in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What does this Flask after_request hook do?

Consider this Flask app code with an after_request hook. What will be the response header 'X-Hello' value for any request?

Flask

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

@app.after_request
def add_header(response: Response):
    response.headers['X-Hello'] = 'World'
    return response

@app.route('/')
def index():
    return 'Hi!'

# Assume app runs normally

A The response will not include any 'X-Hello' header.

B The response will include header 'X-Hello' with value 'Hello'.

C The response will include header 'X-Hello' with value 'World'.

D The code will raise a runtime error because after_request must return a string.

💡 Hint

Remember that after_request modifies the response object before sending it.

The after_request hook modifies the response headers by adding 'X-Hello' with value 'World'. This header will be present in every response.

❓ lifecycle

intermediate

When is the after_request hook called in Flask?

In the Flask request lifecycle, at what point is the after_request function executed?

A Before the view function is called.

B After the view function returns but before the response is sent to the client.

C Only if the view function raises an exception.

D After the response is sent to the client.

💡 Hint

Think about when you want to modify the response before the client sees it.

The after_request hook runs after the view function returns a response but before Flask sends it to the client. It allows modifying the response.

🔧 Debug

advanced

Why does this after_request hook cause an error?

Examine this code snippet. Why will it cause an error when a request is made?

Flask

from flask import Flask
app = Flask(__name__)

@app.after_request
def faulty_hook(response):
    return 'Not a response object'

@app.route('/')
def home():
    return 'Hello'

A Because after_request must return a response object, not a string.

B Because the after_request function must accept no arguments.

C Because the home route returns a string instead of a response object.

D Because the after_request function is missing the @app.route decorator.

💡 Hint

Check what type the after_request function returns.

The after_request hook must return a valid response object. Returning a string causes Flask to raise a TypeError.

📝 Syntax

advanced

Which after_request hook syntax is correct?

Choose the correct syntax for an after_request hook that adds a header 'X-Test' with value 'Yes'.

A

@app.after_request
def add_header():
    response.headers['X-Test'] = 'Yes'
    return response

B

@app.after_request()
def add_header():
    response.headers['X-Test'] = 'Yes'
    return response

C

@app.after_request
def add_header(response):
    response['X-Test'] = 'Yes'
    return response

D

@app.after_request
def add_header(response):
    response.headers['X-Test'] = 'Yes'
    return response

💡 Hint

Remember the after_request function must accept the response argument and return it.

Option D correctly defines the after_request hook with the response parameter and modifies headers properly.

❓ state_output

expert

What is the final response header after multiple after_request hooks?

Given this Flask app with two after_request hooks, what is the final value of the 'X-Count' header in the response?

Flask

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

@app.after_request
def first_hook(response: Response):
    response.headers['X-Count'] = '1'
    return response

@app.after_request
def second_hook(response: Response):
    current = int(response.headers.get('X-Count', '0'))
    response.headers['X-Count'] = str(current + 1)
    return response

@app.route('/')
def index():
    return 'Test'

A 'X-Count' header will be '2'.

B 'X-Count' header will be '1'.

C 'X-Count' header will be '0'.

D The code will raise a KeyError.

💡 Hint

Consider the order in which after_request hooks run and how headers are updated.

Flask calls after_request hooks in the order they are registered. The first sets 'X-Count' to '1', the second increments it to '2'.

Practice

1. What is the main purpose of an after_request hook in Flask?

easy

A. To initialize the Flask app configuration

B. To handle incoming request data before routing

C. To define URL routes for the application

D. To modify the response before it is sent to the client

Solution

1. Step 1: Understand the role of after_request hooks

   After_request hooks run after the view function but before the response is sent to the client.

2. Step 2: Identify what after_request hooks modify

   They receive the response object and can modify it, such as adding headers or logging.

3. Final Answer:

   To modify the response before it is sent to the client -> Option D

4. Quick Check:

   After_request hooks modify response [OK]

Hint: Remember: after_request changes response, not request [OK]

Common Mistakes:

• Confusing after_request with before_request hooks
• Thinking after_request handles incoming data
• Assuming after_request defines routes

2. Which of the following is the correct syntax to register an after_request hook in Flask?

easy

A. @app.after_request\ndef modify_response(response):\n return response

B. @app.route('/after')\ndef modify_response():\n return 'Done'

C. @app.before_request\ndef modify_response(response):\n return response

D. @app.after_response\ndef modify_response(response):\n return response

Solution

1. Step 1: Identify the correct decorator for after_request

   The correct decorator is @app.after_request to register a function that modifies the response.

2. Step 2: Check function signature

   The function must accept one argument (the response) and return it.

3. Final Answer:

   @app.after_request\ndef modify_response(response):\n return response -> Option A

4. Quick Check:

   Use @app.after_request with response param [OK]

Hint: after_request needs @app.after_request decorator [OK]

Common Mistakes:

• Using @app.before_request instead of after_request
• Missing the response parameter in the function
• Using a non-existent decorator like @app.after_response

3. What will be the output headers after this Flask app runs a request?

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

@app.after_request
def add_header(response):
    response.headers['X-Custom'] = 'Hello'
    return response

@app.route('/')
def index():
    return Response('OK')

medium

A. Response with header 'X-Custom' set to 'Hello'

B. Response with no custom headers

C. Error because headers cannot be modified

D. Response with header 'X-Custom' set to 'OK'

Solution

1. Step 1: Understand after_request modifies response headers

   The after_request function adds a header 'X-Custom' with value 'Hello' to the response.

2. Step 2: Check the response returned by the route

   The route returns a Response with body 'OK' but no custom headers initially.

3. Step 3: Confirm header addition

   The after_request hook adds the header before sending, so the final response includes 'X-Custom: Hello'.

4. Final Answer:

   Response with header 'X-Custom' set to 'Hello' -> Option A

5. Quick Check:

   after_request adds headers to response [OK]

Hint: after_request can add headers before sending response [OK]

Common Mistakes:

• Thinking headers cannot be changed after response creation
• Confusing response body with headers
• Assuming after_request runs before route

4. Identify the error in this Flask after_request hook code:

from flask import Flask
app = Flask(__name__)

@app.after_request
def fix_response():
    print('Fixing response')
    return 'Fixed'

medium

A. The function should not return anything

B. The decorator should be @app.before_request

C. The function must accept a response parameter

D. The print statement is not allowed in after_request

Solution

1. Step 1: Check function signature for after_request

   Functions registered with @app.after_request must accept one argument: the response object.

2. Step 2: Analyze the return value

   The function returns a string instead of a response object, which is incorrect.

3. Step 3: Identify the main error

   Missing the response parameter causes Flask to raise an error because it expects the response argument.

4. Final Answer:

   The function must accept a response parameter -> Option C

5. Quick Check:

   after_request functions need response param [OK]

Hint: after_request functions always take response argument [OK]

Common Mistakes:

• Omitting the response parameter in after_request function
• Returning a string instead of a response object
• Confusing after_request with before_request

5. You want to add a security header X-Frame-Options: DENY to all responses except those from the /public route. How can you implement this using after_request hooks?

hard

A. Use before_request to add the header unconditionally

B. Use after_request to check request.path and add header only if path is not '/public'

C. Add the header inside each route function manually

D. Use after_request but always add the header regardless of path

Solution

1. Step 1: Use after_request to modify all responses

   after_request hooks run after every request and can modify the response before sending.

2. Step 2: Check the request path inside after_request

   By accessing request.path, you can conditionally add headers only when the path is not '/public'.

3. Step 3: Implement conditional header addition

   Inside the after_request function, add the header only if request.path != '/public'.

4. Final Answer:

   Use after_request to check request.path and add header only if path is not '/public' -> Option B

5. Quick Check:

   Conditionally add headers in after_request using request.path [OK]

Hint: Check request.path in after_request to add headers conditionally [OK]

Common Mistakes:

• Adding headers unconditionally ignoring route
• Using before_request which can't modify response headers
• Manually adding headers in every route instead of centralized hook