Apa iku middleware ing Django?

Question

Accepted Answer

**Middleware** yaiku kerangka saka hooks sing ngolah **saben request lan response** sacara global, ana ing antarane web server lan views-mu. Saben middleware bisa ngliyati/ngganti requests nalika mlebu lan responses nalika metu — ideal kanggo cross-cutting concerns kayata authentication, security headers, sessions, lan logging.

## Flow request/response liwat middleware

```text
Request  → MW1 → MW2 → MW3 → VIEW
Response ← MW1 ← MW2 ← MW3 ← VIEW

Middleware wraps the view like layers of an onion:
  - on the way IN (request): top-to-bottom
  - on the way OUT (response): bottom-to-top (reverse order)
```

## Django built-in middleware (ing settings.py)

```python
MIDDLEWARE = [
    "django.middleware.security.SecurityMiddleware",          # security headers (HSTS, etc.)
    "django.contrib.sessions.middleware.SessionMiddleware",   # enables request.session
    "django.middleware.common.CommonMiddleware",
    "django.middleware.csrf.CsrfViewMiddleware",              # CSRF protection
    "django.contrib.auth.middleware.AuthenticationMiddleware",# enables request.user
    "django.middleware.clickjacking.XFrameOptionsMiddleware", # clickjacking protection
]
# ORDER MATTERS — e.g. SessionMiddleware must come before AuthenticationMiddleware
```

Kadhaehan fungsionalitas core Django yaiku middleware: sessions (`request.session`), authentication (`request.user`), CSRF protection, lan security headers kabeh teka saka built-in middleware. **Order kuwi penting** — sawetara middleware gumantung marang middleware liya sing kudu mlaku dhisik.

## Ngrancang custom middleware

```python
class TimingMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response          # the next middleware/view

def __call__(self, request):
        # --- code here runs on the way IN (before the view) ---
        import time; start = time.time()

response = self.get_response(request)     # call the next layer (eventually the view)

# --- code here runs on the way OUT (after the view) ---
        response["X-Response-Time"] = f"{time.time() - start:.3f}s"
        return response
```

Middleware yaiku callable: kode sadurunge `self.get_response(request)` mlaku ing request, kode sawise mlaku ing response. Iki ngidini sampeyan tumindak sadurunge lan sawisine view execution.

## Common middleware uses

```text
✓ Authentication / setting request.user
✓ Security headers (CSP, HSTS, X-Frame-Options)
✓ Request/response logging, timing, metrics
✓ Sessions, locale/i18n detection, CORS
✓ Rate limiting, maintenance mode, custom request preprocessing
```

## Middleware versus views/decorators

```text
Middleware → GLOBAL, cross-cutting concerns affecting EVERY (or most) request
Decorators/view logic → per-view concerns specific to certain endpoints
→ Use middleware for app-wide behavior; decorators for selective behavior.
```

## Kenapa iki penting

Middleware yaiku fundamental kanggo cara Django ngolah requests — ngerti babagan iki nerangake carane kathah fungsionalitas core framework lan menehi mekanisme sing tepat kanggo **global, cross-cutting concerns**.

Ngerti bilih sessions, authentication (`request.user`), CSRF protection, lan security headers kabeh teka saka built-in middleware nglirwakaken Django request handling lan nuduhake alasan kenapa features-features iki "mung jalan wae." Ngerti **onion-layer request/response flow** (middleware mbungkus view, ngolah requests saka ndhuwur menyang ngisor lan responses saka ngisor menyang ndhuwur) lan **order kuwi penting** (sawetara middleware gumantung marang middleware liya, kayata authentication butuh sessions dhisik) penting kanggo ngatur Django kanthi bener lan debug issues.

Kemampuan kanggo **ngrancang custom middleware** yaiku berharga kanggo ngimplementasikan perilaku app-wide kanthi rapi — logging, timing, custom headers, rate limiting, maintenance mode — ing sawijining papan tinimbang ngulang-ulang ing views.

Ngerti kapan nggunakake middleware (global concerns sing mengaruh marang kadhaehan requests) versus decorators utawa view logic (per-endpoint concerns) yaiku kaputusan arsitektur kunci.

Middleware yaiku papan Django nangani request/response processing sing berlaku ing sakperlu aplikasi, nggawae penting, praktis-relevan knowledge kanggo kapriye ngerti internals framework lan ngrancang aplikasi sing kuwaé-strukturé kanthi pemisahan bener saka cross-cutting concerns.