[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rt-commit
Subject:    [Rt-commit] rt branch 5.0/pod-update-nginx-client-max-body-size-2 created. rt-5.0.5-83-ga52517500a
From:       BPS Git Server via rt-commit <rt-commit () lists ! bestpractical ! com>
Date:       2023-12-21 18:40:59
Message-ID: 20231221184059.EA2534031F () bps-git ! bestpractical ! com
[Download RAW message or body]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "rt".

The branch, 5.0/pod-update-nginx-client-max-body-size-2 has been created
        at  a52517500ae02a828693c971c9d1d391c27f3ee2 (commit)

- Log -----------------------------------------------------------------
commit a52517500ae02a828693c971c9d1d391c27f3ee2
Author: Ronaldo Richieri <ronaldo@bestpractical.com>
Date:   Thu Dec 14 10:52:04 2023 -0300

    Increase client_max_body_size to 100M in Nginx config example
    
    Nginx has a default limit of 1MB on the size of the request body. This
    is too small in most cases. This commit increases it to 100M that can
    cover most cases.

diff --git a/docs/web_deployment.pod b/docs/web_deployment.pod
index d186800bc2..c86a16d4cc 100644
--- a/docs/web_deployment.pod
+++ b/docs/web_deployment.pod
@@ -195,6 +195,8 @@ With the nginx configuration:
         access_log  /var/log/nginx/access.log;
 
         location / {
+            client_max_body_size 100M;
+
             fastcgi_param  QUERY_STRING       $query_string;
             fastcgi_param  REQUEST_METHOD     $request_method;
             fastcgi_param  CONTENT_TYPE       $content_type;

-----------------------------------------------------------------------


hooks/post-receive
-- 
rt
_______________________________________________
rt-commit mailing list
rt-commit@lists.bestpractical.com
https://lists.bestpractical.com/mailman/listinfo/rt-commit
[prev in list] [next in list] [prev in thread] [next in thread]