Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.2k
[Validator] Highlightextensions instead ofmimeTypes forFile constraint#20893
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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.
I think this is OK, but let's wait for more reviews.
Thanks!
extensions instead ofmimeTypes forFile constraintThere 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.
seesymfony/symfony#47710 (actual changes:symfony/symfony@1613e55)
You should always use the extensions option instead of mimeTypes except if you explicitly don't want to check that the extension of the file is consistent with its content (this can be a security issue).By default, the extensions option also checks the media type of the file.
Thank you@benito103e. |
aafade6 intosymfony:6.4Uh oh!
There was an error while loading.Please reload this page.
You should always use the extensions option instead of mimeTypes except if you explicitly don't want to check that the extension of the file is consistent with its content (this can be a security issue).
By default, the extensions option also checks the media type of the file.