Bird
Raised Fist0
Flaskframework~8 mins

Before_request as middleware alternative in Flask - Performance & Optimization

Choose your learning style10 modes available
Performance: Before_request as middleware alternative
MEDIUM IMPACT
This affects the request handling speed and server response time by controlling when and how middleware logic runs before each request.
Running code before each request to check authentication
Flask
from flask import Flask, request
app = Flask(__name__)

@app.before_request
def fast_check():
    auth = request.headers.get('Authorization')
    if not auth:
        return 'Unauthorized', 401
The check is immediate and non-blocking, allowing the server to respond quickly without delay.
📈 Performance GainReduces request blocking time from 500ms to near 0ms, improving INP significantly.
Running code before each request to check authentication
Flask
from flask import Flask, request
app = Flask(__name__)

@app.before_request
def heavy_check():
    # Simulate heavy processing
    import time
    time.sleep(0.5)  # blocks request handling
    if not request.headers.get('Authorization'):
        return 'Unauthorized', 401
The before_request function blocks the request handling for 0.5 seconds every time, delaying response start.
📉 Performance CostBlocks request handling for 500ms per request, increasing INP and slowing server response.
Performance Comparison
PatternDOM OperationsReflowsPaint CostVerdict
Heavy blocking code in before_requestN/A (server-side)N/AN/A[X] Bad
Lightweight immediate checks in before_requestN/A (server-side)N/AN/A[OK] Good
Rendering Pipeline
The before_request function runs before the main request handler, affecting how fast the server can start processing and sending a response. Heavy or blocking operations here delay the entire request lifecycle.
→Request Handling
→Response Start
⚠️ BottleneckBlocking or slow operations inside before_request delay response start and increase input latency.
Core Web Vital Affected
INP
This affects the request handling speed and server response time by controlling when and how middleware logic runs before each request.
Optimization Tips
1Avoid heavy or blocking operations inside before_request functions.
2Keep before_request logic simple and fast to improve server response time.
3Use asynchronous or deferred processing for expensive tasks outside before_request.
Performance Quiz - 3 Questions
Test your performance knowledge
What is the main performance risk of using a heavy before_request function in Flask?
AIt causes layout shifts on the client side.
BIt increases the size of the HTML sent to the browser.
CIt blocks the server from starting the response quickly, increasing input latency.
DIt slows down CSS rendering in the browser.
DevTools: Network
How to check: Open DevTools Network tab, reload the page, and check the Time to First Byte (TTFB) and response start times for requests.
What to look for: Long TTFB or delayed response start indicates slow server-side middleware like before_request blocking the response.

Practice

(1/5)
1. What is the main purpose of the before_request function in Flask?
easy
A. To send the final response to the client
B. To handle errors after a request has been processed
C. To define routes and their handlers
D. To run code before every request to perform tasks like login checks or logging

Solution

  1. Step 1: Understand the role of before_request

    The before_request function runs before each request to the Flask app, allowing pre-processing like login checks or logging.
  2. Step 2: Compare with other Flask functions

    Functions like error handlers run after requests, and route handlers define endpoints, so they differ from before_request.
  3. Final Answer:

    To run code before every request to perform tasks like login checks or logging -> Option D
  4. Quick Check:

    before_request runs before requests = D [OK]
Hint: before_request runs code before requests start [OK]
Common Mistakes:
  • Confusing before_request with error handlers
  • Thinking before_request sends responses directly
  • Mixing route definition with before_request
2. Which of the following is the correct way to register a before_request function in Flask?
easy
A. @app.before_request\ndef my_function(): pass
B. app.before_request(my_function())
C. app.before_request = my_function()
D. app.before_request = my_function

Solution

  1. Step 1: Recall Flask decorator syntax

    Flask uses decorators like @app.before_request above a function to register it as a before_request handler.
  2. Step 2: Analyze each option

    @app.before_request\ndef my_function(): pass uses the correct decorator syntax. app.before_request(my_function()) calls the function instead of decorating. Options C and D assign incorrectly.
  3. Final Answer:

    @app.before_request\ndef my_function(): pass -> Option A
  4. Quick Check:

    Use @app.before_request decorator = A [OK]
Hint: Use @app.before_request decorator above the function [OK]
Common Mistakes:
  • Calling the function instead of decorating
  • Assigning function instead of decorating
  • Missing the @ symbol for decorator
3. Given this Flask code, what will be the output when accessing /?
from flask import Flask, request, abort
app = Flask(__name__)

@app.before_request
def check_auth():
    if request.args.get('token') != 'secret':
        abort(401)

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

# Assume app runs normally
medium
A. Displays 'Welcome!' if URL has ?token=secret, else 401 Unauthorized error
B. Always displays 'Welcome!' regardless of token
C. Always returns 401 Unauthorized error
D. Raises a syntax error due to missing return in before_request

Solution

  1. Step 1: Understand the before_request check

    The check_auth function runs before every request and aborts with 401 if the 'token' query parameter is not 'secret'.
  2. Step 2: Analyze the route behavior

    If the token is correct, the request proceeds to home() which returns 'Welcome!'. Otherwise, the request is stopped early with 401.
  3. Final Answer:

    Displays 'Welcome!' if URL has ?token=secret, else 401 Unauthorized error -> Option A
  4. Quick Check:

    before_request aborts if token wrong = C [OK]
Hint: before_request can block requests early with abort() [OK]
Common Mistakes:
  • Thinking before_request must return a value
  • Assuming route runs even if abort called
  • Confusing query parameters with headers
4. Identify the error in this Flask code using before_request:
from flask import Flask
app = Flask(__name__)

@app.before_request
def setup():
    print('Setup done')

@app.route('/')
def index():
    return 'Hello'
medium
A. Missing parentheses in @app.before_request decorator
B. No return statement in before_request function causes error
C. No error; code works correctly
D. Route function must be named before_request

Solution

  1. Step 1: Check before_request function requirements

    The before_request function can run code and does not need to return anything unless it wants to stop the request.
  2. Step 2: Verify decorator and route correctness

    The decorator syntax is correct, and the route function is properly defined with a return statement.
  3. Final Answer:

    No error; code works correctly -> Option C
  4. Quick Check:

    before_request can have no return = B [OK]
Hint: before_request functions don't need to return unless blocking [OK]
Common Mistakes:
  • Expecting before_request to always return a response
  • Confusing decorator syntax with function call
  • Thinking route function must be named before_request
5. You want to use before_request to check if a user is logged in by verifying a session key. If not logged in, redirect to /login. Which code snippet correctly implements this?
hard
A. from flask import redirect, session def check_login(): if 'user' not in session: return redirect('/login') app.before_request(check_login())
B. from flask import redirect, session @app.before_request def check_login(): if 'user' not in session: return redirect('/login')
C. from flask import redirect, session @app.before_request def check_login(): if session['user'] is None: return redirect('/login')
D. from flask import redirect @app.before_request def check_login(): if session.get('user') == False: return redirect('/login')

Solution

  1. Step 1: Check session key existence safely

    from flask import redirect, session @app.before_request def check_login(): if 'user' not in session: return redirect('/login') uses 'user' not in session which safely checks if the user is logged in.
  2. Step 2: Confirm correct decorator and redirect usage

    from flask import redirect, session @app.before_request def check_login(): if 'user' not in session: return redirect('/login') uses the @app.before_request decorator and returns a redirect response correctly to stop further processing.
  3. Final Answer:

    from flask import redirect, session @app.before_request def check_login(): if 'user' not in session: return redirect('/login') -> Option B
  4. Quick Check:

    Use @app.before_request and check 'user' in session = A [OK]
Hint: Use @app.before_request and check session key presence [OK]
Common Mistakes:
  • Calling the function instead of decorating
  • Checking session key with wrong condition
  • Not returning redirect to stop request
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard