🔍 Code Extractor

Flask error handler that catches HTTP 500 Internal Server Errors and renders a custom error page with a generic error message.

Purpose

This function serves as a centralized error handler for all internal server errors (HTTP 500) in a Flask application. It provides a user-friendly error page instead of exposing stack traces or technical details to end users. The handler is registered via the @app.errorhandler(500) decorator and is automatically invoked whenever an unhandled exception occurs during request processing.

Source Code

def internal_error(error):
    return render_template('error.html', error="Internal server error"), 500

Parameters

Parameter Details

error: The exception or error object that triggered the 500 error. This parameter is automatically passed by Flask's error handling mechanism and contains information about the error that occurred. The function does not use this parameter directly but it must be present in the signature for Flask's error handler protocol.

Return Value

Returns a tuple containing: (1) the rendered HTML template 'error.html' with an 'error' context variable set to 'Internal server error', and (2) the HTTP status code 500. Flask uses this tuple to construct the HTTP response sent to the client.

Dependencies

• flask

Required Imports

from flask import Flask
from flask import render_template

Usage Example

from flask import Flask, render_template

app = Flask(__name__)

@app.errorhandler(500)
def internal_error(error):
    return render_template('error.html', error="Internal server error"), 500

@app.route('/test-error')
def test_error():
    # This will trigger the 500 error handler
    raise Exception('Test error')

if __name__ == '__main__':
    app.run(debug=False)

Best Practices

• Always log the actual error details server-side before returning the generic message to users
• Consider passing the error object to a logging service for debugging purposes
• Ensure the error.html template exists and is properly styled to match your application's design
• In production, avoid exposing detailed error information to end users for security reasons
• Consider adding different error handlers for different HTTP error codes (404, 403, etc.)
• The error parameter should be logged or monitored even if not displayed to users
• Test error handlers in a non-debug mode as Flask's debug mode may override custom error handlers
• Consider implementing error tracking services (like Sentry) to capture and monitor 500 errors

Tags

Similar Components

AI-powered semantic similarity - components with related functionality:

• function internal_error_v2 96.4% similar

  Flask error handler that catches internal server errors (HTTP 500), logs them, and renders a user-friendly error page.

  From: /tf/active/vicechatdev/vice_ai/app.py

• function internal_error 90.1% similar

  Flask error handler that catches internal server errors (HTTP 500), logs them, and returns a standardized JSON error response.

  From: /tf/active/vicechatdev/docchat/app.py

• function handle_exception 78.8% similar

  Flask error handler that catches all unhandled exceptions, logs them, and returns a generic JSON error response with HTTP 500 status.

  From: /tf/active/vicechatdev/vice_ai/new_app.py

• function not_found 68.7% similar

  Flask error handler function that renders a custom error page when a 404 (Page Not Found) error occurs.

  From: /tf/active/vicechatdev/vice_ai/app.py

• function not_found_error 67.5% similar

  Flask error handler that renders a custom error page when a 404 (Page Not Found) error occurs.

  From: /tf/active/vicechatdev/full_smartstat/app.py