You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’d expect this to prevent the upload, but it actually allows the file to be uploaded before validation is run server-side. That, while a little frustrating for CMS users who have slow connections, does work for smaller files, however...
If post_max_size is set to 10mb, the field is set to 1mb, and the user attempts to upload a 40mb file, they receive a useless error message: a 400 error code and There has been an error (or other webserver error message). Error logs show:
PHP Warning: POST Content-Length of 40500753 bytes exceeds the limit of 10485760 bytes in Unknown on line 0, referer:
Attempting to upload files via AssetAdmin does produce error messages prior to uploading, so client-side validation is obviously possible somehow.
Expected results
If the set UploadField max file size is exceeded, there is client-side validation alerting the user
The file is prevented from being uploaded/does not reach the server
Tested with 1.3.3
I’d expect this to prevent the upload, but it actually allows the file to be uploaded before validation is run server-side. That, while a little frustrating for CMS users who have slow connections, does work for smaller files, however...
If
post_max_size
is set to 10mb, the field is set to 1mb, and the user attempts to upload a 40mb file, they receive a useless error message: a 400 error code andThere has been an error
(or other webserver error message). Error logs show:Attempting to upload files via
AssetAdmin
does produce error messages prior to uploading, so client-side validation is obviously possible somehow.Expected results
PRs
The text was updated successfully, but these errors were encountered: