client intended to send too large body: 1441104 bytes

확인 범위

이 문서는 화면 또는 로그에 표시된 client intended to send too large body: 1441104 bytes 문구가 NGINX 유지보수자 Trac 공식 원문의 항목과 일치하는지 확인합니다.

원문 발췌

ches -specs=/u sr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-prot ection -fPIC' --with-ld-opt='-Wl,-z,relro -Wl,-z,now -pie' Description I have the next configuration and client_max_body_size doesn't matter in a named location. I have errors "413 Request Entity Too Large" in log files. Everything is OK when I move client_max_body_size to server {} from named locations. error log: client intended to send too large body: 1441104 bytes, client: 10.178.67.87, server: loki, request: "POST /loki/api/v1/push HTTP/1.1", host: "loki" access log: 10.178.67.87 - eissd [18/Feb/2022:14:37:55 +0500] eissd_dev "POST /loki/api/v1/push HTTP/1.1" 413 306 "Apache-HttpClient/4.5.13 (Java/17.0.2)" 0.086 - Attachments (1) loki.conf​ (2.5 KB ) - added by gadskypapa@… 4 years ago. Download all attachments as: .zip Oldest first Newest first Threaded Show comments Show property changes Change History (3) by gadskypapa@…, 4 years ago Attachment: loki.conf​ added comment:1 by gadskypapa@…, 4 years ago I reworked my config and it looks much better. And I sorted out my problem. But anyway client_max_body_size doesn't work in named locations. Maybe it should be clarified in documentation at least. upstream loki { server 127.0.0.1:3100; } map "$uri:$http_upgrade" $loki_connection { "~/loki/api/v1/tail:.+" $http_connection; default ""; } map $http_x_scope_orgid $tenant { eissd "eissd"; eissd_dev "eissd"; crmb2b "crmb2b"; default "okd4p"; } server { listen 443 ssl http2; server_name loki; access_log /var/log/nginx/loki.access.log loki; error_log /var/log/nginx/loki.error.log notice; location /metrics { proxy_pass http_://loki; allow 10.178.67.3/32; deny all; } location /loki/api/v1/tail { proxy_pass http_://loki; 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_set_header Connection $loki_connection; proxy_set_header Upgrade $http_upgrade; proxy_set_header Authorization ; auth_basic "Loki"; auth_basic_user_file .htpasswd.loki.$tenant; } location /loki/api/v1/push { proxy_pass http_://loki; proxy_request_buffering on; client_body_buffer_size 32k; client_max_body_size 6m; auth_basic "Loki"; auth_basic_user_file .htpasswd.loki.$tenant; } location / { proxy_pass http_://loki; auth_basic "Loki"; auth_basic_user_file .htpasswd.loki.$tenant; } } comment:2 by SorinGFS@…, 4 years ago I confirm that client_max_body_size does not work in named location (nginx 1.21.6). In fact, in this case nginx seem not to consider the named location as the selected location block, but instead considers the selected location block the one which triggered named location selection. Example: location /upload/ { # this is considered selected location block and client_body_max_size works! client_body_max_size 100m; try_files $uri @upload; } location @upload { # this is NOT considered selected location block and client_

확인 절차

1. 현재 화면 또는 로그에서 client intended to send too large body: 1441104 bytes 문구를 확인합니다.
2. 위 원문 발췌와 문구를 비교합니다.
3. 문구가 일치하면 이 문서의 출처 링크에서 적용 환경과 원문 전체를 확인합니다.

주의

이 문서는 문구 식별 범위로 제한합니다. 출처가 직접 설명하지 않는 원인, 설정 변경, 권한 변경 또는 복구 절차를 이 문서만으로 실행하지 마십시오.