Never follow redirect in the middleware

[conico974]

Configure the middleware to not follow redirects, ensuring that redirects are handled by the client instead.

This was causing 404 for most redirects on the first call after an invalidation in 2C.

[linear]

RND-7820 404 error on newly published pages in Gitbook discussions

[changeset-bot]

⚠️ No Changeset found

Latest commit: 37103a1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[github-actions]

Summary of the deployments:

Version	URL	Status
Vercel	https://gitbook-v2-nswlgg40i-gitbook.vercel.app	✅
Cloudflare	https://fbf5fe53-gitbook-open-v2-preview.gitbook.workers.dev	✅

Test content

Site	2v	2c
GitBook	https://gitbook-v2-nswlgg40i-gitbook.vercel.app/url/gitbook.com/docs	https://fbf5fe53-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs
E2E	https://gitbook-v2-nswlgg40i-gitbook.vercel.app/url/gitbook.gitbook.io/test-gitbook-open	https://fbf5fe53-gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.gitbook.io/test-gitbook-open

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
customers-v2 (Inspect)	👍 Changes approved	34 changed	Aug 13, 2025, 10:51 AM
v2-cloudflare (Inspect)	👍 Changes approved	6 changed	Aug 13, 2025, 10:55 AM
v2-vercel (Inspect)	✅ No changes detected	-	Aug 13, 2025, 10:54 AM

[gregberge]

What does it fix?

[conico974]

What does it fix?

On 2c for redirects from within a page (i.e. not from the middleware), the first ever call could return a 404. This was not necessarily noticeable, as most of them were for background request that would never be accessed. And subsequent request worked just fine.
This caused flakyness for these tests as well