Cómo llega una solicitud a su vista

Every Django page begins as an HTTP request. A browser asks for a URL, and Django's job is to answer with a response. 🌐

A web server like Nginx receives the raw request first. It handles networking, then hands the request off to Django to do the real work.

WSGI is the standard interface between the web server and Django. It turns the incoming request into something your Python code can read.

Django ships a callable in wsgi.py. The server calls it for each request, and Django takes over from there to route and respond.

Before your view, the request passes through middleware. Each layer can inspect or tweak the request, like adding security checks.

Django reads urls.py and matches the requested path against your patterns. The first pattern that matches wins the request.

If the path is /about/, Django finds the matching pattern and notes which view should handle it. No match means a 404.

Django calls your view function and passes it the request object. This is where your own code finally takes control.

Your view must return an HttpResponse. Django takes that object and hands it back up the chain toward the browser.

The response travels back through middleware in reverse order. Layers can add headers or compress content before it leaves.

The web server sends the finished response across the network. The browser renders it, completing one full request cycle. ✅

A request flows from server to WSGI, through middleware, to the URL resolver, then your view, and back out as a response. That loop is Django. 🎉