fix: Avoid warning from exif_imagetype() on corrupted png images #456
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
ctrlaltca
changed the title
ctrlaltca
force-pushed
the
corrupted_img
branch
from
2782fd6 to
9445e61
Compare
|
Php 8.5 CI seems to be failing for unrelated reasons |
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.
Hello, thank you for this useful library that always served me well.
Today I found a possible problem in the usage of
exif_imagetypethat in case of malformed images may generate a warning:The image is obviously problematic / corrupted, but avoiding the warning let the parsing complete successfully.
I've used the same approach already implemented for
getimagesize()a few lines later