Description
1) we should make sure that the serialization of resizing when multiple users are uploading is working properly.
2) apply a limit on the dimensions and file size of the image. An image with large dimensions can occupy a lot of memory space when resized.
Description below is based on checking file size solely and is thus outdated.
Flash based upload: change javascript such that flash upload gets a limit that is configured in the repo. Make sure that the error msg for reaching the limit is localized.
Wicket based upload: check server side image size. Basic idea for the feedback is: Throw hippo exception when image too large. Change the default error dialog such that hippo exception is properly displayed instead of displaying 'an error occurred'
Latter needs check with Frank
Attachments
Issue Links
- discovered while testing
-
CMS-6699 Backport - Regression - Image is not opened (properly) after upload when flash is turned-off
- Closed
-
CMS-6407 Regression - Image is not opened (properly) after upload when flash is turned-off
- Closed
- relates to
-
CMS-5970 Reduce chance of out-of-memory during image upload (patch attached)
- Closed
-
CMS-6747 Add Asset Validator to default repo configuration
- Closed
-
CMS-6476 BACKPORT 5970: 7.6 (2.20.xx) Reduce chance of out-of-memory during image upload (patch attached)
- Closed
- testing discovered
-
CMS-6392 Regression - CMS throws http status 500 error when user attempts to upload an image (Flash off)
- Closed
-
CMS-6393 Exceptions while uploading an image in CMS
- Closed