fix: No body for 101, 204, 205, or 304 status code

[vicb]

Fix a KI when browser cache was enabled by pulling the fix from opennextjs/opennextjs-aws#683

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0d341ee

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

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/@opennextjs/cloudflare@195

commit: 0d341ee

[petebacondarwin]

What is a KI?

I feel uncomfortable about landing "fixes" with no tests.
How hard would it be to add tests that prove this bump to the aws dependency fixes the problem?

[vicb]

KI = known issue (See the README update).

I tested locally with the blog example, reloading the page would generated the error as it adds a body to a 304. This might be possible to e2e but I'm not sure how e2e behaves regarding to cache.

I'm confident that the issue is fixed.

[conico974]

LGTM