Merged
Conversation
Add a 'Content negotiation' subsection to the Backend for Frontend guide showing how to use rewrites with header matching to serve Markdown (or other formats) from the same URL based on the Accept header. Covers: - Rewrite config with has/header matching for text/markdown - Route Handler with generateStaticParams for pre-rendering - Vary: Accept header and its role in CDN/proxy cache correctness - Link to rewrites API reference in related links Co-authored-by: Joseph <[email protected]>
|
Cursor Agent can help with this pull request. Just |
nextjs-bot
added
created-by: Next.js DevEx team
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
molebox
reviewed
Feb 27, 2026
molebox
reviewed
Feb 27, 2026
molebox
reviewed
Feb 27, 2026
molebox
requested changes
Feb 27, 2026
molebox
approved these changes
Feb 27, 2026
icyJoseph
added a commit
that referenced
this pull request
Feb 27, 2026
<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? Added a new "Content negotiation" subsection to the Backend For Frontend (BFF) guide. Updated the `related` links in the frontmatter of the BFF guide to include "rewrites". ### Why? To document how to implement content negotiation using Next.js rewrites and Route Handlers, specifically for serving different content types (e.g., Markdown) based on the `Accept` header. This includes explaining the role of the `Vary: Accept` header for correct caching behavior. ### How? A new subsection was added to `docs/01-app/02-guides/backend-for-frontend.mdx`. The section includes a `next.config.js` rewrite example using `has` to match the `Accept` header. A corresponding Route Handler example (`app/docs/md/[...slug]/route.ts`) demonstrates serving Markdown content. The documentation explains the `Vary: Accept` header and its implications for caching. The `related` links in the frontmatter were updated to point to the rewrites documentation. Closes NEXT- Fixes # --> --- [Slack Thread](https://vercel.slack.com/archives/C07BS1WEYAZ/p1772118031912479?thread_ts=1772118031.912479&cid=C07BS1WEYAZ) <p><a href="https://cursor.com/agents/bc-2c93f44d-958d-5c0b-abe0-a2b36aa76f19"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-2c93f44d-958d-5c0b-abe0-a2b36aa76f19"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </p> --------- Co-authored-by: Cursor Agent <[email protected]> Co-authored-by: Joseph <[email protected]> Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
icyJoseph
added a commit
that referenced
this pull request
Feb 27, 2026
![https://cursor.com/assets/images/open-in-web-dark.png"><source](https://cursor.com/assets/images/open-in-web-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-web-light.png"><img](https://cursor.com/assets/images/open-in-web-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a](https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"><source](https://cursor.com/assets/images/open-in-cursor-dark.png"><source){kind=link}
![https://cursor.com/assets/images/open-in-cursor-light.png"><img](https://cursor.com/assets/images/open-in-cursor-light.png"><img){kind=link}
![https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </p](https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </p){kind=link}
## Summary Backports documentation fixes and improvements from canary to the `next-16-1` branch. ### Included commits: - `757ab17e54` In-Depth Explanation of React Version Handling Doc (#89426) - `fe0bb2fc51` Next.js sticky scroll standards (#90197) - `d13d1ba23b` docs: improve form guide consistency and validation examples (#90361) - `c23f3434a3` docs: fixes typo in manifest.mdx regarding Route Handler note (#90394) - `dcf11d111b` docs: clarify that next upgrade is for 16.1.x+ (#90435) - `da0cbcce76` Add not-found.js / notFound() links to Status Codes section (#88332) - `ae79ae55eb` docs: add Docker Standalone and Docker Export examples to Deploying page (#90386) - `bb813afd49` docs(deploying): add Hostinger Web Apps Hosting to Node.js deployment options (#90246) - `15fcfb9ce4` docs: fix navigationType value and variable name in useReportWebVitals (#90599) - `080e1b3` docs: Accept header content negotiation (#90607) --------- Co-authored-by: Abhishek Mardiya <[email protected]> Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com> Co-authored-by: Jimmy Lai <[email protected]> Co-authored-by: Cursor Agent <[email protected]> Co-authored-by: Mary Lavanitha <[email protected]> Co-authored-by: Tyler Arthur <[email protected]> Co-authored-by: Karl Horky <[email protected]> Co-authored-by: Kristiyan Velkov <[email protected]> Co-authored-by: Wyatt Johnson <[email protected]> Co-authored-by: kristiyan.velkov <[email protected]> Co-authored-by: agneliutkiene <[email protected]> Co-authored-by: Mimori <[email protected]> Co-authored-by: Joseph <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Slack Thread