(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 nextcloud/docker#1796 Signed-off-by: Josh Richards <[email protected]>
joshtrichards · Aug 11, 2023 · f9c4a3f · f9c4a3f
1 parent 5e8b945
commit f9c4a3f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git 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 <https://httpd.apache.org/docs/current/en/mod/core.html#limitrequestbody>`_
+* `LimitRequestBody <https://httpd.apache.org/docs/current/en/mod/core.html#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 <https://httpd.apache.org/docs/current/mod/mod_ssl.html#sslrenegbuffersize>`_
 * `Timeout <https://httpd.apache.org/docs/current/mod/core.html#timeout>`_