Rate limiting for protection in Flask - Step-by-Step Execution

Concept Flow - Rate limiting for protection

Client sends request

↓

Check request count for client

↓

Is count < limit?

No→Reject request with error

Yes↓

Process request

↓

Increment request count

↓

Send response

↓

Wait for time window reset

↓

Reset request count

This flow shows how a server checks the number of requests from a client, allows or blocks requests based on a limit, and resets counts after a time window.

Execution Sample

Flask

from flask import Flask, request, jsonify
from flask_limiter import Limiter
from flask_limiter.util import get_remote_address

app = Flask(__name__)
limiter = Limiter(app, key_func=get_remote_address, default_limits=["3 per minute"])

@app.route("/data")
@limiter.limit("3 per minute")
def data():
    return jsonify({"message": "Success"})

This Flask app limits each client IP to 3 requests per minute on the /data route.

Execution Table

Step	Client IP	Request Count	Condition (count < 3?)	Action	Response
1	192.168.1.10	0	Yes	Process request	200 Success
2	192.168.1.10	1	Yes	Process request	200 Success
3	192.168.1.10	2	Yes	Process request	200 Success
4	192.168.1.10	3	No	Reject request	429 Too Many Requests
5	192.168.1.10	3	No	Reject request	429 Too Many Requests
6	192.168.1.10	Reset after 1 minute	Yes	Process request	200 Success

💡 Request count reaches limit 3, further requests are blocked until reset after 1 minute.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After reset
request_count	0	1	2	3	3	0

Key Moments - 2 Insights

Why does the 4th request get rejected even though the client is still sending requests?

Because the request count reached the limit of 3 (see execution_table step 4), the server blocks further requests until the time window resets.

What happens to the request count after one minute?

The request count resets to 0 (see variable_tracker After reset), allowing the client to send requests again.

Visual Quiz - 3 Questions

Look at the execution table, what is the request count at step 3?

A 3

B 2

C 1

D 0

💡 Hint

Check the 'Request Count' column at step 3 in the execution_table.

At which step does the server start rejecting requests?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look for 'Reject request' action in the execution_table.

If the limit was changed to 5 requests per minute, how would the request count at step 4 change?

A It would be 3

B It would be 5

C It would be 4

D It would reset to 0

💡 Hint

With a higher limit, the count increments normally until the new limit is reached.

Concept Snapshot

Rate limiting in Flask uses a counter per client IP.
Each request increments the count.
If count exceeds limit (e.g., 3/min), requests are blocked.
Count resets after time window (e.g., 1 minute).
Use flask_limiter for easy setup.

Full Transcript

Rate limiting protects a Flask app by counting requests from each client IP. When a client sends a request, the server checks how many requests that client made recently. If the count is below the limit, the request is processed and the count increases. If the count reaches the limit, further requests are rejected with a 429 error until the time window resets and the count goes back to zero. This prevents clients from overwhelming the server with too many requests in a short time. The example code uses the flask_limiter library to enforce a limit of 3 requests per minute on the /data route.

Practice

1. What is the main purpose of rate limiting in a Flask application?

easy

A. To control how many requests a user can make in a given time period

B. To speed up the database queries

C. To change the user interface dynamically

D. To encrypt user data automatically

Solution

1. Step 1: Understand rate limiting concept

   Rate limiting restricts the number of requests a user can send to prevent overload.

2. Step 2: Identify the purpose in Flask apps

   It protects the app from abuse and excessive traffic by limiting requests.

3. Final Answer:

   To control how many requests a user can make in a given time period -> Option A

4. Quick Check:

   Rate limiting = request control [OK]

Hint: Rate limiting limits requests per time to protect apps [OK]

Common Mistakes:

• Confusing rate limiting with database optimization
• Thinking it changes UI behavior
• Assuming it encrypts data automatically

2. Which of the following is the correct way to initialize Flask-Limiter in a Flask app?

easy

A. limiter = Limiter(app)

B. limiter = Limiter(key_func=get_remote_address)

C. limiter = Limiter(app, key_func=get_remote_address)

D. limiter = Limiter()

Solution

1. Step 1: Check Flask-Limiter initialization syntax

   Flask-Limiter requires the Flask app instance and a key function to identify clients.

2. Step 2: Identify correct parameters

   Passing both app and key_func=get_remote_address is necessary for proper setup.

3. Final Answer:

   limiter = Limiter(app, key_func=get_remote_address) -> Option C

4. Quick Check:

   Limiter init requires app and key_func [OK]

Hint: Always pass app and key_func when creating Limiter [OK]

Common Mistakes:

• Omitting the app parameter
• Not specifying key_func
• Calling Limiter without arguments

3. Given this Flask route with rate limiting:

@app.route('/api')
@limiter.limit('2 per minute')
def api():
    return 'OK'

What happens if a user sends 3 requests within one minute?

medium

A. The third request returns 'OK' as usual

B. The third request is blocked with a 429 Too Many Requests error

C. All requests are blocked

D. The server crashes

Solution

1. Step 1: Understand the rate limit decorator

   The decorator limits requests to 2 per minute per user.

2. Step 2: Analyze the third request behavior

   The third request exceeds the limit and triggers a 429 error response.

3. Final Answer:

   The third request is blocked with a 429 Too Many Requests error -> Option B

4. Quick Check:

   Exceeding limit = 429 error [OK]

Hint: Requests over limit get 429 error response [OK]

Common Mistakes:

• Assuming all requests succeed
• Thinking server crashes on limit
• Believing all requests get blocked

4. You wrote this code but rate limiting is not working:

limiter = Limiter()

@app.route('/test')
@limiter.limit('5 per minute')
def test():
    return 'Test'

What is the likely problem?

medium

A. The limit string format is incorrect

B. The function name is invalid

C. The route decorator is missing

D. Limiter was not given the Flask app instance

Solution

1. Step 1: Check Limiter initialization

   Limiter must be initialized with the Flask app instance to work.

2. Step 2: Identify missing app parameter

   Here, Limiter() is called without app, so rate limiting won't activate.

3. Final Answer:

   Limiter was not given the Flask app instance -> Option D

4. Quick Check:

   Missing app in Limiter = no limit [OK]

Hint: Always pass app to Limiter for it to work [OK]

Common Mistakes:

• Ignoring the need to pass app to Limiter
• Thinking limit string format causes failure
• Assuming route decorator is missing

5. You want to apply different rate limits for logged-in users and guests in Flask using Flask-Limiter. Which approach correctly implements this?

hard

A. Use a custom key_func that returns user ID if logged in, else IP address

B. Apply the same limit to all users without distinction

C. Set limit only on the route without key_func customization

D. Disable rate limiting for logged-in users completely

Solution

1. Step 1: Understand user identification for rate limiting

   To differentiate limits, key_func must identify users uniquely.

2. Step 2: Use custom key_func logic

   Return user ID for logged-in users, IP for guests to apply different limits.

3. Final Answer:

   Use a custom key_func that returns user ID if logged in, else IP address -> Option A

4. Quick Check:

   Custom key_func distinguishes users [OK]

Hint: Custom key_func distinguishes users for different limits [OK]

Common Mistakes:

• Applying same limit to all users ignoring login status
• Not customizing key_func for user identity
• Disabling limits for logged-in users without reason