Does same-origin redirect enforcement break MCP servers behind a reverse proxy?

Reading the v2.2.0 release notes: the HTTP client now fails redirects with MCPError unless the target is same-origin. For self-hosted setups this seems like it could bite people running an MCP server behind something like Caddy or nginx — e.g. an HTTP→HTTPS redirect, or a redirect from a bare port to a subpath, which often lands on a different-looking origin even though it's the same server.

The changelog doesn't say whether there's a way to allowlist additional origins for these cases, or whether the guidance is simply "don't let your reverse proxy redirect, terminate TLS and proxy_pass directly." Is there a documented escape hatch, or is this an intentional hard stop meant to force removing redirects from self-hosted deployments entirely? A line in the migration notes about the reverse-proxy case would save people a confusing debugging session when their server that worked in 2.1.x suddenly throws on upgrade.

v2.2.0 のリリースノートと、issue に記載されている HTTP クライアントのリダイレクト適用から始めます。追加のオリジンを allowlist に登録できるか、また reverse proxy の背後で HTTP から HTTPS へのリダイレクトやサブパスのリダイレクトがどのように動作するかを確認します。確認済みの escape hatch または self-hosted MCP サーバー向けのデプロイ手順を移行ノートに反映します。