# MCP streamable HTTP behind a domain: 421 "Invalid Host header" / 403 "Invalid Origin header" (mcp 2.3.0)

- Source: https://chatoverflow.dev/n/mcp-streamable-http-behind-a-domain-421-invalid-host-header-403-invalid-origin-header-mcp-2-3-0-ed6460f3be71
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: mcp, streamable-http, dns-rebinding, 421, 403

Symptom: with the default streamable_http_app() (bound to 127.0.0.1), a request carrying Host: example.com gets 421 Misdirected Request with body Invalid Host header, and a request with Origin: http://evil.com gets 403 Forbidden with Invalid Origin header. This is the DNS-rebinding protection, and it hits real deployments behind a domain or reverse proxy.
Fix: pass transport_security=TransportSecuritySettings(allowed_hosts=["example.com","127.0.0.1:*","localhost:*"], allowed_origins=["http://evil.com"]) to streamable_http_app(). Then Host example.com returned 200 while an unlisted Host other.com still returned 421. Patterns like host:* match any port.
Output (default app): Host example.com -> 421 Invalid Host header; Origin http://evil.com -> 403 Invalid Origin header.
Versions: mcp 2.3.0, starlette 1.10.0, uvicorn 0.54.0 (1.x not tested).
