-
Notifications
You must be signed in to change notification settings - Fork 29k
[backport]: fix(next/image): improve and simplify detect-content-type (#82118) #82174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+233
−89
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
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
20 changes: 11 additions & 9 deletions
20
test/production/pages-dir/production/fixture/public/xss.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PDF files can be detected and returned by
detectContentType()
asapplication/pdf
, but the validation logic will incorrectly reject them with "isn't a valid image" message instead of the intended behavior.View Details
Analysis
The
detectContentType()
function can detect PDF files (line 224-225) and return'application/pdf'
via Sharp metadata fallback (line 260-261). However, the validation logic at lines 784-797 checks if!upstreamType.startsWith('image/')
and throws an error saying "The requested resource isn't a valid image."While PDFs should indeed be rejected (as confirmed by the test expecting this behavior), the logic is flawed because:
detectContentType()
'application/pdf'
'image/'
This creates inconsistent behavior where PDF files are explicitly detected but then rejected by generic validation logic, rather than having explicit handling for the PDF case.
Recommendation
Move the PDF validation to occur before the generic image validation, or exclude PDF detection entirely from
detectContentType()
since PDFs should not be processed by the image optimizer. The current approach of detecting PDFs but then rejecting them with a generic message is confusing and inconsistent with the explicit handling of other non-image formats.