mirror of
https://github.com/cloudflare/vinext.git
synced 2026-05-09 08:25:34 +02:00
[PR #788] [MERGED] fix(app-router): use override semantics when merging middleware headers into HTML responses #847
Labels
No labels
enhancement
enhancement
good first issue
help wanted
nextjs-tracking
nextjs-tracking
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vinext#847
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/cloudflare/vinext/pull/788
Author: @NathanDrake2406
Created: 4/8/2026
Status: ✅ Merged
Merged: 4/8/2026
Merged by: @james-elicx
Base:
main← Head:fix/bug3-html-header-merge📝 Commits (1)
13336defix(app-router): use override semantics when merging middleware headers into HTML responses📊 Changes
2 files changed (+6 additions, -7 deletions)
View changed files
📝
packages/vinext/src/server/app-page-response.ts(+1 -5)📝
tests/app-page-response.test.ts(+5 -2)📄 Description
Summary
mergeMiddlewareResponseHeadersinbuildAppPageHtmlResponseso HTML responses follow the same middleware merge semantics as RSC responsesSet-Cookie,Vary) and override singular headers (for exampleCache-Control)Cache-Controloverride withSet-Cookie/VaryaccumulationVerification
vp test run tests/app-page-response.test.tsvp test run tests/app-route-handler-response.test.ts🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.