fix: re-encode Next.js decoded slug segments in REST route handler#15799
Open
andershermansen wants to merge 2 commits intopayloadcms:mainfrom
Open
fix: re-encode Next.js decoded slug segments in REST route handler#15799andershermansen wants to merge 2 commits intopayloadcms:mainfrom
andershermansen wants to merge 2 commits intopayloadcms:mainfrom
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
1 participant
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?
Fixes file downloads returning 404 for filenames containing
#when served through the REST API.Why?
Next.js catch-all
[...slug]params decodes URL-encoded segments before passing them to route handlers. So a request for/api/media/file/document%20%23123.pdfarrives with slug segments['media', 'file', 'document #123.pdf'].These decoded segments are joined and passed to
path-to-regexpfor endpoint matching. The:filenamepattern uses[^\/#\?]+?which excludes#and?— so the match fails and returns 404.How?
Re-encode each slug segment with
encodeURIComponentbefore joining:handleEndpoints already uses match(endpoint.path, { decode: decodeURIComponent }), so params are decoded back to their original values after matching
Also adds a test that creates a file with # in the filename and verifies it can be served via REST.
Fixes #15798