fix(next): support HEAD requests in REST routes#16761
Open
raunak3208 wants to merge 1 commit into
Open
Conversation
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
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.
What?
Adds explicit
HEADsupport to the Next.js REST route handlers by exporting:from
packages/next/src/routes/rest/index.ts.Why?
/api/media/file/*routes were returning404forHEADrequests while returning200for the same resource withGET.This causes inconsistent behavior for clients and proxies using
HEADrequests for lightweight existence checks and does not align with RFC 9110 §9.3.2 behavior expectations.How?
The REST route handlers already export
GET,POST,PATCH, etc., but did not explicitly export aHEADhandler.This PR maps
HEADto the existingGEThandler so thatHEADrequests follow the same routing and response logic without returning a response body.Fixes #16754