Error handling in production in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of error handling in production in Flask?

To catch and manage errors gracefully so users see friendly messages instead of raw error details, improving user experience and security.

beginner

How do you configure Flask to show custom error pages in production?

By using error handler decorators like @app.errorhandler(404) to define functions that return custom HTML or messages for specific HTTP errors.

beginner

Why should you disable debug mode in Flask when deploying to production?

Because debug mode shows detailed error info and code, which can expose sensitive data and security risks to users.

intermediate

What is the role of logging in Flask error handling for production?

Logging records error details in files or external systems so developers can review and fix issues without exposing details to users.

intermediate

How can you handle unexpected exceptions globally in a Flask app?

By creating a handler for Exception with @app.errorhandler(Exception) to catch all unhandled errors and respond with a generic message.

What decorator is used in Flask to handle a 404 error?

A @app.route('/404')

B @app.handle_error(404)

C @app.errorhandler(404)

D @app.catch(404)

The @app.errorhandler(404) decorator defines a function to handle 404 Not Found errors.

Why should Flask's debug mode be off in production?

A It slows down the app

B It prevents logging

C It disables error handling

D It shows detailed error info that can leak sensitive data

Debug mode reveals detailed error information that can expose sensitive data to users.

What is a good practice for user experience when an error occurs in production?

A Display a friendly error page

B Redirect to homepage silently

C Show raw error tracebacks

D Reload the page automatically

Displaying a friendly error page helps users understand something went wrong without confusion.

How can Flask developers keep track of errors without showing them to users?

A Use print statements

B Use logging to save error details

C Ignore errors in production

D Show errors only to admins

Logging saves error details for developers to review later without exposing them to users.

Which error handler catches all unhandled exceptions in Flask?

A @app.errorhandler(Exception)

B @app.errorhandler(500)

C @app.errorhandler(404)

D @app.errorhandler(Error)

Using @app.errorhandler(Exception) catches all exceptions not handled by other specific handlers.

Explain how to set up custom error pages in a Flask app for production use.

Think about how Flask lets you catch specific errors and respond with your own pages.

Describe why logging is important in production error handling and how Flask supports it.

Consider how developers find and fix bugs without showing errors on the website.

Practice

1. What is the main purpose of using @app.errorhandler in a Flask application?

easy

A. To catch specific errors and provide custom responses

B. To speed up the application startup

C. To automatically restart the server on errors

D. To log user activities

Solution

1. Step 1: Understand the role of @app.errorhandler

   This decorator is used to catch specific HTTP or application errors in Flask.

2. Step 2: Recognize its use for custom responses

   It allows developers to return user-friendly error pages or messages instead of default error traces.

3. Final Answer:

   To catch specific errors and provide custom responses -> Option A

4. Quick Check:

   Error handling = custom responses [OK]

Hint: Errorhandler decorates functions to catch and respond to errors [OK]

Common Mistakes:

• Thinking it restarts the server automatically
• Confusing errorhandler with logging functions
• Assuming it speeds up app startup

2. Which of the following is the correct syntax to handle 404 errors in Flask?

easy

A. @app.error(404)
def not_found(error):
return 'Not found', 404

B. @app.errorhandler(404)
def not_found(error):
return 'Page not found', 404

C. @app.handle_error(404)
def not_found():
return 'Page missing', 404

D. @app.catch_error(404)
def not_found(error):
return '404 error', 404

Solution

1. Step 1: Identify the correct decorator name

   The correct Flask decorator for error handling is @app.errorhandler.

2. Step 2: Confirm function signature and return

   The function should accept an error parameter and return a response with the error code.

3. Final Answer:

   @app.errorhandler(404)\ndef not_found(error):\n return 'Page not found', 404 -> Option B

4. Quick Check:

   Correct decorator and function signature = @app.errorhandler(404) def not_found(error): return 'Page not found', 404 [OK]

Hint: Use @app.errorhandler with error code and error param [OK]

Common Mistakes:

• Using wrong decorator names like @app.handle_error
• Omitting the error parameter in the function
• Returning without the status code

3. Given this Flask code snippet, what will the user see if a 500 error occurs?

@app.errorhandler(500)
def internal_error(error):
    return 'Something went wrong, please try later.', 500

medium

A. The message: 'Something went wrong, please try later.' with status 500

B. A detailed Python traceback error page

C. A blank page with status code 500

D. The default Flask 404 error page

Solution

1. Step 1: Understand the errorhandler function

   The function returns a custom message and status code 500 when a 500 error occurs.

2. Step 2: Identify the user-visible output

   The user will see the returned string message with HTTP status 500, not the default traceback.

3. Final Answer:

   The message: 'Something went wrong, please try later.' with status 500 -> Option A

4. Quick Check:

   Custom error message shown = The message: 'Something went wrong, please try later.' with status 500 [OK]

Hint: Custom errorhandler returns your message, not default trace [OK]

Common Mistakes:

• Expecting Flask's default error page instead of custom message
• Thinking a blank page will appear
• Confusing 500 error with 404 error page

4. What is wrong with this Flask error handler code?

@app.errorhandler(403)
def forbidden():
    return 'Access denied', 403

medium

A. The return statement must include a JSON response

B. The decorator should be @app.handle_error

C. The function must accept an error parameter

D. The status code 403 is invalid

Solution

1. Step 1: Check function signature for errorhandler

   Flask error handler functions must accept the error argument to receive error details.

2. Step 2: Identify missing error parameter

   The function forbidden lacks the required error parameter.

3. Final Answer:

   The function must accept an error parameter -> Option C

4. Quick Check:

   Error handler function needs error param = The function must accept an error parameter [OK]

Hint: Error handler functions always take an error argument [OK]

Common Mistakes:

• Omitting the error parameter in handler functions
• Using wrong decorator names
• Assuming JSON response is mandatory

5. You want to show a friendly error page for all unhandled exceptions in production without exposing debug info. Which Flask setup is best?

hard

A. Use @app.route('/error') to manually show errors

B. Set app.debug = True to see detailed errors

C. Remove all error handlers to let Flask show default error pages

D. Use @app.errorhandler(Exception) to catch all errors and return a simple message

Solution

1. Step 1: Understand catching all exceptions

   Using @app.errorhandler(Exception) catches all unhandled errors globally.

2. Step 2: Provide user-friendly message without debug info

   Returning a simple message hides technical details, improving user experience and security.

3. Final Answer:

   Use @app.errorhandler(Exception) to catch all errors and return a simple message -> Option D

4. Quick Check:

   Global error handler with simple message = Use @app.errorhandler(Exception) to catch all errors and return a simple message [OK]

Hint: Catch Exception globally to hide debug info in production [OK]

Common Mistakes:

• Enabling debug mode in production
• Relying on default Flask error pages
• Using routes instead of error handlers for errors