Rate limiting for protection in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is rate limiting in web applications?

Rate limiting is a technique to control how many requests a user or client can make to a server in a given time. It helps protect the app from overload and abuse.

beginner

How does Flask-Limiter help in rate limiting?

Flask-Limiter is an extension that makes it easy to add rate limits to Flask routes. It tracks requests and blocks users who exceed limits.

beginner

What is a common rate limit rule format in Flask-Limiter?

A common rule looks like '5 per minute', meaning a user can make 5 requests every minute before being blocked.

intermediate

Why is rate limiting important for API endpoints?

It prevents too many requests from one user or bot, which can crash the server or cause slowdowns. It also stops abuse like brute force attacks.

intermediate

How can you customize rate limits per user in Flask?

You can use a key function that identifies users (like IP or user ID) so limits apply individually. Flask-Limiter supports this with the key_func parameter.

What does '10 per hour' mean in rate limiting?

A 10 requests allowed every hour

B 10 requests allowed per second

C 10 users allowed per hour

D 10 requests blocked every hour

It means a user can make 10 requests in one hour before being blocked.

Which Flask extension helps implement rate limiting easily?

A Flask-Migrate

B Flask-Login

C Flask-Mail

D Flask-Limiter

Flask-Limiter is designed to add rate limiting to Flask apps.

Why should rate limiting consider user identity like IP or user ID?

A To block all users at once

B To allow unlimited requests

C To apply limits fairly per user

D To speed up the server

Using user identity helps apply limits individually, preventing one user from affecting others.

What happens when a user exceeds the rate limit?

A Their requests are blocked or delayed

B They get faster responses

C They get logged out automatically

D Nothing happens

Exceeding the limit usually blocks or delays further requests to protect the server.

Which of these is NOT a benefit of rate limiting?

A Stopping brute force attacks

B Allowing unlimited requests

C Preventing server overload

D Improving app stability

Rate limiting restricts requests; it does not allow unlimited requests.

Explain how you would add rate limiting to a Flask route using Flask-Limiter.

Think about the steps from setup to applying limits on routes.

Describe why rate limiting is important for protecting web applications and APIs.

Consider what happens if too many requests come in quickly.

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