Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P2
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.3.0
-
Labels:
-
Template:customfield_11100 21876
-
Sprint:EPAM BatchLoader Sprint 6, EPAM BatchLoader Sprint 7
-
Story Points:5
-
Development Team:Folijet
-
Epic Link:
Description
Find limitations for the file upload functionality. Any browser limitation to the file size? For this spike, assume a maximum of 3 browsers will be investigated.
Results: wiki page describing steps taken, plus:
Once investigations done, decide if there should be a few more stories, and if so create them (or work with A-M to create the UI stories):
1. What to recommend to users that have very large files to upload (alternate method). Make sure tenant is aware that their server must have enough free space to accommodate such big files.
2. If browser limitation found, consider adding some sort of message/warning in the UI if they attempt to upload a file that is too large.
3. Maybe add an option for the tenant to set a file size limitation into the file upload (maybe we don't implement, but recommend for Stripes Force to add to the central component)
TestRail: Results
Attachments
Issue Links
- relates to
-
MODAFILT-5 No need to try to turn the body into a Json if the contentType is not application/json
-
- Closed
-
-
MODDATAIMP-68 Add uploaded file size validation dependent on systems resources
-
- Closed
-
-
OKAPI-693 Introduce filter request-log to avoid buffering HTTP content in memory
-
- Closed
-
-
RMB-321 Improve file upload mechanism to avoid memory leaks
-
- Closed
-
-
UIDATIMP-86 File upload: Show error message on UI when there is not enough server space for uploaded file(s)
-
- Closed
-
-
UXPROD-656 Data Import (Batch Importer for Bib Acq) Infrastructure and Planning
-
- Closed
-