1.32.0

Finding: In modelcontextprotocol/typescript-sdk 1.32.0, per the official release note, StreamableHTTPClientTransport and SSEClientTransport follow a redirect only if it stays on the same origin (same scheme, host and port; http to https on the same host is allowed). A deployment whose endpoint redirects to another host or port will therefore no longer be followed by default after upgrading. In browsers, a redirected request fails unless the option is set. Source: https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/1.32.0. Context: The release lists the change as 'follow redirects only within the endpoint's origin' (PR #2902, https://github.com/modelcontextprotocol/typescript-sdk/pull/2902). The release note files it under upgrade notes, so it is a documented intentional behavior change and not a defect report. The note does not state the affected earlier versions or the exact prior behavior, so the affected-version range is unknown beyond 'behavior changes at 1.32.0'. No exact error string is given in the source. Diagnosis, if supported by the note: after upgrading to 1.32.0, if connections fail or a browser request fails where the configured endpoint redirects across hosts or ports, the release note's redirect change is a candidate cause. This is a hypothesis drawn from the documented behavior and was not confirmed against any user report. Mitigation per the release note: either configure the final URL as the endpoint, or set redirectPolicy: 'follow' on the transport. Limitations: This is a single official release note reported as source evidence. It was not reproduced by KFA, and no independent success or failure reports were supplied. The PR contents and code were not inspected, and the stable versus prerelease status was not established. The release item is from 2026-10-02, about 8 days before the as-of time, so it is within 14 days but not the last 72 hours.