Project

General

Profile

Defect #2106

Max file upload exception is not propagated to frontend.

Added by Radek Tomiška about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Low
Category:
Attachment manager
Target version:
Start date:
03/09/2020
Due date:
% Done:

100%

Estimated time:
Affected versions:
Milestones:

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.


Related issues

Related to CzechIdM - Task #2195: Max file upload - server configuration documentationClosed04/08/2020

Related to CzechIdM containers - Task #2116: Allow max uploaded file size to be up to 100MBClosed03/11/2020

History

#1 Updated by Radek Tomiška about 1 year ago

  • Subject changed from Max file upload exception is not propagatd to frontend. to Max file upload exception is not propagated to frontend.

#2 Updated by Radek Tomiška about 1 year ago

  • Status changed from New to In Progress

#3 Updated by Radek Tomiška about 1 year ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Radek Tomiška to Vít Švanda
  • % Done changed from 0 to 70

This issue is related to application server setting (https://www.baeldung.com/spring-maxuploadsizeexceeded#tomcat-configuration).
I improved error message in product only and removed some typo.

Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/4b719df7575a61aa76ee0dd5ee2ac00462210964

Doc:
https://wiki.czechidm.com/devel/documentation/application_configuration/dev/backend#attachment_storage

Could you please test tomcat setting above and provide me a feedback please? After that I will ask sys to update instalation guides.

#4 Updated by Vít Švanda about 1 year ago

  • Assignee changed from Vít Švanda to Ondrej Husník

#5 Updated by Ondrej Husník about 1 year ago

  • 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?

#6 Updated by Radek Tomiška about 1 year ago

  • Status changed from In Progress to Needs feedback
  • Assignee changed from Radek Tomiška to Ondrej Husník

Thx for feedback!
ad1) Properties without idm prefix cannot be changed by idm configuration service (is already in doc, this is the reason, why two sections are there)
ad2) True, i forgot to change it in one place :) (doc + other profiles was ok), commit: https://github.com/bcvsolutions/CzechIdMng/commit/8d6dd28aac9d4a048ed364aa67c1ec4ce6e85b28
ad3) Yes, and it can be controlled (overriden) by selected profile

#7 Updated by Ondrej Husník about 1 year ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Ondrej Husník to Radek Tomiška
  • % Done changed from 70 to 100

#8 Updated by Radek Tomiška about 1 year ago

  • Status changed from Resolved to Closed

#9 Updated by Radek Tomiška about 1 year ago

  • Related to Task #2195: Max file upload - server configuration documentation added

#10 Updated by Petr Fišer about 1 year ago

  • Related to Task #2116: Allow max uploaded file size to be up to 100MB added

Also available in: Atom PDF

Go to top