From f9c4a3fce44074f27e5334e536b65ee45713d9e2 Mon Sep 17 00:00:00 2001 From: Josh Richards Date: Fri, 11 Aug 2023 08:44:15 -0400 Subject: [PATCH] (big_file_upload_configuration) Note new Apache LimitRequestBody default Apache's default for this changed from 0 (unlimited) to 1 GiB. This impacts non-chunking client transactions. Resolves: #35778 and #37695 and documents needed adjustments applicable to various others like https://github.com/nextcloud/docker/issues/1796 Signed-off-by: Josh Richards --- .../configuration_files/big_file_upload_configuration.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/admin_manual/configuration_files/big_file_upload_configuration.rst b/admin_manual/configuration_files/big_file_upload_configuration.rst index db3082771..8e188dc96 100644 --- a/admin_manual/configuration_files/big_file_upload_configuration.rst +++ b/admin_manual/configuration_files/big_file_upload_configuration.rst @@ -65,7 +65,7 @@ for how to configure those values correctly: Apache ^^^^^^ -* `LimitRequestBody `_ +* `LimitRequestBody `_ (In Apache HTTP Server <=2.4.53 this defaulted to unlimited, but now defaults to 1 GiB. The new default limits uploads from non-chunking clients to 1 GiB. If this is a concern in your environment, override the new default by either manually setting it to ``0`` or to a value similar to that used for your local environment's PHP ``upload_max_filesize / post_max_size / memory_limit`` parameters.) * `SSLRenegBufferSize `_ * `Timeout `_