fix: shouldSkipRedirect incorrectly skips cross-domain redirects

[devinle]

Summary

• Adds host comparison check in shouldSkipRedirect to ensure cross-domain redirects are never skipped
• Fixes an issue where redirects configured from one domain to another with the same pathname would result in 404 errors instead of proper redirects

Fixes #941

Changes

packages/core/src/utils/fetchRedirect.ts:

• Added early return in shouldSkipRedirect when linkURL.host !== redirectURL.host
• Cross-domain redirects now bypass the pathname comparison logic and are properly followed

Test plan

• Added test for cross-domain redirect with same pathname
• Added test for cross-domain redirect with different pathname
• CI tests pass

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk: small redirect-skip logic tweak plus targeted tests; main behavioral change is that cross-domain redirects will now be followed even when path/query match.

Overview
Fixes fetchRedirect incorrectly treating cross-domain redirects as “no-op” when the pathname/query match by updating shouldSkipRedirect to never skip redirects when host differs.

Adds MSW handlers and unit tests covering cross-domain redirects for both same-path and different-path cases, and includes a patch changeset for @headstartwp/core.

^{Written by Cursor Bugbot for commit 1e62299. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
headstartwp-app-router	Ready	Preview, Comment	Feb 2, 2026 7:59pm
headstarwp	Ready	Preview, Comment	Feb 2, 2026 7:59pm

[changeset-bot]

🦋 Changeset detected

Latest commit: 1e62299

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@headstartwp/core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR