Why middleware matters in Django - The Real Reasons

The Big Idea

Discover how a few lines of middleware can save you hours of repetitive work and bugs!

The Scenario

Imagine building a web app where you must check user login, log every request, and handle errors manually in every view function.

The Problem

Doing these tasks manually means repeating code everywhere, risking mistakes, and making updates slow and confusing.

The Solution

Django middleware lets you write these common tasks once and have them run automatically for every request and response.

Before vs After

✗ Before

def view(request):
    if not user_logged_in(request):
        return redirect('login')
    log_request(request)
    try:
        # view logic
        response = ...  # define response here
    except Exception:
        handle_error()
    return response

✓ After

class AuthMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response
    def __call__(self, request):
        if not user_logged_in(request):
            return redirect('login')
        return self.get_response(request)

class LogMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response
    def __call__(self, request):
        log_request(request)
        return self.get_response(request)

What It Enables

It enables clean, reusable, and centralized control over how requests and responses are handled across your whole Django app.

Real Life Example

For example, a middleware can automatically add security headers to every page without changing each view.

Key Takeaways

Manual checks in every view cause repeated code and errors.

Middleware runs code automatically on all requests and responses.

This makes your app easier to maintain and more secure.