(Nginx + Gunicorn) 時 nginx 400 request line is too large (4360 4094)
查看nginx下面兩個參數 值是否知足nginx
client_header_buffer_size 512k;
large_client_header_buffers 4 512k;代理
知足依然出現it
若是nginx是作反向代理
設置gunicorn 參數
--limit-request-line 8188 （默認是4094）反向代理
相關文章
- 1. SpringBoot 400 Bad Request(Request header is too large)
- 2. Nginx 413 Request Entity Too Large
- 3. nginx 414 Request-URI Too Large
- 4. Nginx 413 Request Too Large 錯誤
- 5. 關於nginx作代理，uwsgi gunicorn等服務器作後端時
- 6. Request header is too large
- 7. ingress-nginx-controller 414 Request—URI Too Large
- 8. Nginx 踩坑 413 Request Entity Too Large
- 9. Nginx中413 request entity too large問題
- 10. Nginx 出現413 Request Entity Too Large
- 更多相關文章...
- • Docker 安裝 Nginx - Docker教程
- • SVG
- SVG 教程 - • Docker容器實戰(八) - 漫談 Kubernetes 的本質
- • Spring Cloud 微服務實戰(三) - 服務註冊與發現
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
歡迎關注本站公眾號,獲取更多信息
相關文章
- 1. SpringBoot 400 Bad Request(Request header is too large)
- 2. Nginx 413 Request Entity Too Large
- 3. nginx 414 Request-URI Too Large
- 4. Nginx 413 Request Too Large 錯誤
- 5. 關於nginx作代理，uwsgi gunicorn等服務器作後端時
- 6. Request header is too large
- 7. ingress-nginx-controller 414 Request—URI Too Large
- 8. Nginx 踩坑 413 Request Entity Too Large
- 9. Nginx中413 request entity too large問題
- 10. Nginx 出現413 Request Entity Too Large