"""Local-web attack surface: session, CSRF, Origin/Host checks, default headers. The app binds to 127.0.0.1, so the attacker is not a remote client but another page in the user's browser (concept §15, "Local web attack"): any site can issue requests to ``http://127.0.0.1:8000`` and can embed ```` against media endpoints. The defenses stack, because each one alone has a hole: * **Host** must be a loopback name — a DNS rebinding host that resolves to 127.0.0.1 passes the browser's origin rules but not this check. * **Origin**, when the browser sends one, must be this exact origin (scheme, host, port). There is no CORS middleware at all, so a foreign page can never *read* a response even if it manages to send a request. * **Sec-Fetch-Site** rejects cross-site loads that carry no Origin, which is what an ```` or ``