Defect #2106
closed
Max file upload exception is not propagated to frontend.
Added by Radek Tomiška about 4 years ago.
Updated about 4 years ago.
Category:
Attachment manager
Description
When max file upload size is exceeded, then frontend doesn't obtain response => no message is shown to user about something is wrong / or white page is shown.
Show correct error meesege.
- Subject changed from Max file upload exception is not propagatd to frontend. to Max file upload exception is not propagated to frontend.
- Status changed from New to In Progress
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Vít Švanda
- % Done changed from 0 to 70
- Assignee changed from Vít Švanda to Ondrej Husník
- Status changed from Needs feedback to In Progress
- Assignee changed from Ondrej Husník to Radek Tomiška
I did test of this task and announcement about exceeding max upload size is shown properly. That's great, but I found some subtle issues.
1) Setting of size limits in *.properties file cannot be overridden in configuration. This overriding doesn't work. Even after expected need of IdM restart.
2) It would be good to change allowed units in .../ app/.properties file hint to KB, MB. There are Kb, Mb which doesn't work.
3) I tested this task on uploading of import/export batch which is implemented in Core module. But its upload limit is controlled by setting from ../ app/.../.properties file. Is it OK?
- Status changed from In Progress to Needs feedback
- Assignee changed from Radek Tomiška to Ondrej Husník
- Status changed from Needs feedback to Resolved
- Assignee changed from Ondrej Husník to Radek Tomiška
- % Done changed from 70 to 100
- Status changed from Resolved to Closed
- Related to Task #2195: Max file upload - server configuration documentation added
- Related to Task #2116: Allow max uploaded file size to be up to 100MB added
Also available in: Atom
PDF
