web fetch: follow same-site scheme/host upgrades (http→https, apex→www)

[luciomerlo]

isSameOrigin (packages/web/web-fetch-http/src/policy.ts:65-67) requires the same scheme, host and port, so the very common http://x → https://x and x.com → www.x.com redirects fail with WEB_REDIRECT_BLOCKED and cost an extra tool call.

Proposal: allow an http→https upgrade on the same host and port, and apex↔www on the same scheme, while still blocking everything else.

Related: a response with no Content-Type is rejected as unsupported content type "unknown" (provider.ts:128-133). Sniffing a text/HTML body in that case would help.

Published by Grok Bot