如何提升Django+Nginx+uWSGI页面加载大小限制？

开发者阿泽

2026-8-4

问题描述

我用Nginx + uWSGI搭配Django（通过daphne）部署单页网站时遇到加载截断问题：页面添加较多HTML元素时，内容会中途停止加载——比如60行表格仅显示前30行，表格后内容完全缺失；30个文本卡片仅加载部分，后续内容消失；但15个卡片可完整加载。浏览器开发者工具无任何报错，仅超过数量阈值后的HTML元素直接缺失。

Nginx配置

# build_check_nginx.conf

# the upstream component nginx needs to connect to
upstream django {
    server unix:///path/to/build_check.sock; # for a file socket
}

# configuration of the server
server {
    # the port your site will be served on
    listen      80;
    # the domain name it will serve for
    server_name x.xx.xxx.xxx; # substitute your machine's IP address or FQDN
    charset     utf-8;

    # max upload size
    client_max_body_size 800M;   # adjust to taste
    client_body_timeout 3600;
    client_body_buffer_size 800M;
    sendfile_max_chunk 800M;        
    # http and server
    client_header_buffer_size 800M;

    # Django media
    location /media  {
        alias /path/to/site/media;  # your Django project's media files - amend as required
    }

    location /static {      
        client_body_timeout 3600;
        client_body_buffer_size 800M;
        client_max_body_size 800M;
        sendfile_max_chunk 800M;

        alias /path/to/static; # your Django project's static files - amend as required
    }

    # Finally, send all non-media requests to the Django server.
    location / {
        proxy_read_timeout 600s;
        uwsgi_read_timeout 600s;
        uwsgi_send_timeout 600s;
        client_body_timeout 3600;
        client_body_buffer_size 800M;
        client_max_body_size 800M;
        sendfile_max_chunk 800M;        

        uwsgi_pass  django;
        include     /path/to/uwsgi_params; # the uwsgi_params file you installed
    }
}

注：已尝试调整所有文档提及的大小相关参数。

uWSGI配置

# build_check_uwsgi.ini file
[uwsgi]

# Django-related settings
# the base directory (full path)
chdir           = /path/to/site
# Django's wsgi file
module          = build_check_site.wsgi:application
# callable = application
# process-related settings
# master
 master          = true
# maximum number of worker processes
processes       = 5
# the socket (use the full path to be safe
socket          = /path/to/build_check.sock
socket-timeout  = 900s
# ... with appropriate permissions - may be needed
chmod-socket    = 666
uid = [redacted]
gid = [redacted]
# clear environment on exit
vacuum          = true
safe-pidfile = /tmp/build_check.pid
limit-as = 900 # limit the project to 900 MB
max-requests = 7000 # respawn processes after serving 5000 requests
daemonize = /path/to/build_check.log
http-timeout = 900s
websockets-max-size = 9000
websocket-max-size = 9000
chunked-input-limit = 1000000
chunked-input-timeout = 400000
post-buffering = 1282900
buffer-size = 12829000
post-buffering-bufsize = 12829000
fastrouter-buffer-size = 12829000
http-buffer-size = 12829000

注：所有能找到的uWSGI大小相关参数均已调大。

补充信息

半加载状态Firefox内存快照
完全加载状态Firefox内存快照

解决思路

修正Daphne与uWSGI的部署逻辑：你提到使用Daphne，但当前配置用uWSGI处理所有请求，Daphne专为ASGI/WebSocket场景设计，混合部署可能导致长响应截断。可通过Nginx区分路径，将渲染大量HTML的请求直接交给Daphne：

location / {
    try_files $uri @daphne;
}

location @daphne {
    proxy_pass http://127.0.0.1:8001; # 假设Daphne运行在8001端口
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_read_timeout 600s;
}

同时启动Daphne：daphne -b 0.0.0.0 -p 8001 build_check_site.asgi:application

排查uWSGI响应截断细节：
- 开启uWSGI详细日志，添加logto = /path/to/uwsgi_detailed.log和verbose = true，查看响应发送时是否有截断记录；
- 临时注释limit-as参数测试，该参数限制进程内存，若内存接近阈值可能强制终止响应；
- 添加disable-logging = false确保所有请求日志被记录，排查是否有请求中途终止的迹象。
Nginx额外配置检查：
- 若改用Daphne代理，在对应location块添加proxy_buffering off;，避免Nginx缓存响应导致截断；
- 查看Nginx错误日志（通常在/var/log/nginx/error.log），排查是否存在upstream prematurely closed connection类错误，此类错误说明uWSGI提前终止了连接。
Django渲染层面验证：
- 在本地开发环境（runserver）渲染相同数量的元素，确认是否能完整输出，排除模板渲染本身的问题；
- 检查模板中是否存在未闭合的HTML标签，大量元素时未闭合标签可能导致浏览器解析异常，表现为内容“截断”；
- 尝试用StreamingHttpResponse替代普通HttpResponse，分块发送响应，避免一次性生成大响应导致缓冲区溢出。
网络层面排查：
- 在服务器本地用curl请求目标页面并保存响应内容，若本地curl得到的内容完整，说明问题出在Nginx到客户端的传输环节；若curl也截断，问题则在uWSGI或Django；
- 检查服务器防火墙、安全组是否有数据包大小限制，部分防火墙会截断超过特定大小的HTTP响应。

内容的提问来源于stack exchange，提问作者simon lombard

如何提升Django+Nginx+uWSGI页面加载大小限制？

Nginx配置 #

uWSGI配置 #

补充信息 #

Nginx配置

uWSGI配置

补充信息