Yes, it was it! Thanks a lot!

When you hit the limit, the _javascript_ does not complain. Is there a way to intercept the Apache event denying the upload? Or it is better to have the _javascript_ to check itself for the limit?

Hi Yuri,

I suspect this may be an Apache restriction on LimitRequestBody [1].  The default value for this is 1073741824 bytes which is 1 GiB.  I think you can put this in any Apache configuration file but as you want to make sure this is maintained if you migrate your repository, I would recommend adding it to your archive's securevhost.conf, as I would assume you have HTTPS enabled and therefore file uploads would only happen over HTTPS.  A setting something like:

LimitRequestBody 2147483648

Would up the max upload limit to 2GB, once you reload your webserver.

Regards

David Newman

[1] https://httpd.apache.org/docs/2.4/mod/core.html#limitrequestbody

On 19/01/2023 16:33, Yuri via Eprints-tech wrote:

CAUTION: This e-mail originated outside the University of Southampton.

Hi!

  I've just discovered that I can upload until 1GB without any problem
(progress bar working correctly). If I upload above 1GB, the upload bar
stay at 0% and never move, and no upload is done. In the browser, I can
see it calls /cgi/users/ajax/upload_progress?progressid=<a string> about
every 1 or 2 seconds, and the transferred bytes are zero. Below 1GB, I
can see the number of transferred bytes progressing.

  How can I check what is the problem? It is Eprints 3.3.15


*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: https://eur03.safelinks.protection.outlook.com/?url="">
*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url="">