E_REQUEST_ENTITY_TOO_LARGE / 413 Request Entity Too Large #6

Open
opened 2024-02-15 12:23:19 +00:00 by brutho · 8 comments
Member

Error when the upload is too large
epmpty cache and login logout doesn't help
another browser helps

Error when the upload is too large epmpty cache and login logout doesn't help another browser helps
brutho added the
bug
label 2024-02-15 12:23:19 +00:00
kaiarn was assigned by brutho 2024-02-15 12:23:19 +00:00
brutho added this to the (deleted) project 2024-02-15 12:23:19 +00:00
Owner

@brutho: I would need the link to the used test data. Thank you in advance.

@brutho: I would need the link to the used test data. Thank you in advance.
Author
Member

@kaiarn I tried to upload all the data that Porras shared with us on Gitea
https://rhea.geologie.ac.at/apps/files_sharing/accept/ocinternal:6265

142.666.015 Byte (148,4 MB auf dem Volume) für 17 Objekte

@kaiarn I tried to upload all the data that Porras shared with us on Gitea https://rhea.geologie.ac.at/apps/files_sharing/accept/ocinternal:6265 142.666.015 Byte (148,4 MB auf dem Volume) für 17 Objekte
Member

@kaiarn As you could imagine, the problem doesn't occur when using a single small PDF file (<1 Mb) like:
Tethys 217 - DataDescription_GEOFAST.pdf
615.256 bytes
(in the same Sample data folder in Nextcloud)

@kaiarn As you could imagine, the problem doesn't occur when using a single small PDF file (<1 Mb) like: [Tethys 217 - DataDescription_GEOFAST.pdf](https://rhea.geologie.ac.at/s/TErkCo2szmRxFeF) 615.256 bytes (in the same _[Sample data](https://rhea.geologie.ac.at/s/XHtXjt6YQbnCTc8)_ folder in Nextcloud)
Author
Member

after changing the nginx configuration there is a new error message

/etc/nginx/nginx.conf
client_max_body_size 500M;

E_REQUEST_ENTITY_TOO_LARGE: request entity too large

75_export_4326.jpg 143 MB (150 080 065 Bytes)

after changing the nginx configuration there is a new error message `/etc/nginx/nginx.conf` client_max_body_size 500M; E_REQUEST_ENTITY_TOO_LARGE: request entity too large 75_export_4326.jpg 143 MB (150 080 065 Bytes)
brutho changed title from 413 Request Entity Too Large to E_REQUEST_ENTITY_TOO_LARGE / 413 Request Entity Too Large 2024-02-20 10:42:51 +00:00
Owner

@brutho
E_REQUEST_ENTITY_TOO_LARGE:
Simply increasing the NGINX upload size is not sufficient here. Similar to PHP, there's also an adjustable upload size for Node.js. The setting has been adjusted. Testing in this regard can be resumed.

@brutho E_REQUEST_ENTITY_TOO_LARGE: Simply increasing the NGINX upload size is not sufficient here. Similar to PHP, there's also an adjustable upload size for Node.js. The setting has been adjusted. Testing in this regard can be resumed.
Member

The error message is no longer appearing.

The error message is no longer appearing.
Member

When editing the draft of a new submission it is possible to remove small files and "Save" the changes. However with files of some size (e.g. 124Mb zip), if it is removed and user click "save", the page remains unresponsive.

Any other action apparently doesn't generate any response in the page. If the window is closed and the app access again, the user is still logged in.

When going to the Submitter menu, only the Release button trigger a change in the page:
image

So is not possible to Edit or Delete the submission in progress.

When editing the draft of a new submission it is possible to remove small files and "Save" the changes. However with files of some size (e.g. 124Mb zip), if it is removed and user click "save", the page remains unresponsive. Any other action apparently doesn't generate any response in the page. If the window is closed and the app access again, the user is still logged in. When going to the Submitter menu, only the Release button trigger a change in the page: ![image](/attachments/f82be015-fbc9-4d5d-b41c-74cac15b90e1) So is not possible to Edit or Delete the submission in progress.
Member

(Firefox) Another issue

Workflow followed:

  1. Create new publication
  2. Upload a small Zip file (7Mb)
  3. Save
  4. Check draft and edit it (correctly)
  5. Added another file (gpkg) -> Error message, not accepted
  6. Added another file (txt) -> Correctly accepted
  7. Added another file (jpeg) -> Correctly accepted
  8. Save draft
  9. Edit draft -> wrong (multiple times) uploaded files on display:

image

  1. Click "Clear" to remove all
  2. Save changes
  3. Edit draft -> all the files again on display
(Firefox) Another issue Workflow followed: 1. Create new publication 2. Upload a small Zip file (7Mb) 3. Save 4. Check draft and edit it (correctly) 5. Added another file (gpkg) -> Error message, not accepted 6. Added another file (txt) -> Correctly accepted 7. Added another file (jpeg) -> Correctly accepted 8. Save draft 9. Edit draft -> wrong (multiple times) uploaded files on display: ![image](/attachments/64e27f1b-ba0a-4bfb-8aeb-7d948352061e) 10. Click "Clear" to remove all 11. Save changes 12. Edit draft -> all the files again on display
108 KiB
porfra added this to the Iteration 1: All "Bugs" are solved milestone 2024-07-17 14:06:18 +00:00
porfra reopened this issue 2024-07-29 13:59:39 +00:00
Sign in to join this conversation.
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: geolba/tethys.backend#6
No description provided.