Opened 6 months ago

Closed 5 months ago

Last modified 4 months ago

#2343 closed defect (invalid)

net::ERR_CONTENT_LENGTH_MISMATCH

Reported by: krsvital@… Owned by:
Priority: major Milestone:
Component: nginx-core Version:
Keywords: CONTENT_LENGTH Cc:
uname -a: Linux BIGREC7 4.18.0-310.el8.x86_64 #1 SMP Tue Jun 8 00:24:50 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.21.7
built by gcc 8.5.0 20210514 (Red Hat 8.5.0-1) (GCC)
built with OpenSSL 1.1.1k FIPS 25 Mar 2021
TLS SNI support enabled
configure arguments: --with-http_ssl_module --with-http_v2_module --with-http_realip_module --with-threads --with-stream_ssl_module --add-module=/var/db/pack/nginx_modules/headers-more-nginx-module-0.33

Description

this error apears every fourth time

84.22.140.8 - - [12/Apr/2022:20:31:40 +0700] "GET /s/OyfqK3rxkMbeQej/download HTTP/1.1" 200 1075126 "[link]" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.60 Safari/537.36 Edg/100.0.1185.29"
84.22.140.8 - - [12/Apr/2022:20:31:44 +0700] "GET /s/OyfqK3rxkMbeQej/download HTTP/1.1" 200 1075126 "[link]" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.60 Safari/537.36 Edg/100.0.1185.29"
84.22.140.8 - - [12/Apr/2022:20:31:47 +0700] "GET /s/OyfqK3rxkMbeQej/download HTTP/1.1" 200 1075126 "[link]" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.60 Safari/537.36 Edg/100.0.1185.29"
84.22.140.8 - - [12/Apr/2022:20:31:51 +0700] "GET /s/OyfqK3rxkMbeQej/download HTTP/1.1" 200 637814 "[link]" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.60 Safari/537.36 Edg/100.0.1185.29"

last content length is 637814 (have to be 1075126), but in header content length is correct

URL for checking:
https://mycloud.g-service.ru:4430/s/OyfqK3rxkMbeQej/download

Change History (3)

comment:1 by Maxim Dounin, 6 months ago

The size as logged in the access log corresponds to the amount of bytes actually sent to the client. The fact that it doesn't match the expected size of the response suggests that the error happened during sending the response body.

The file seems to be returned by the backend server. Most likely, there is a problem with the backend server, or with the response buffering by nginx (typical problems include invalid permissions on proxy_temp_path / fastcgi_temp_path, or lack of available free space).

Please check the error log for further details. Corresponding error is expected to be logged at the error level or higher.

comment:2 by Maxim Dounin, 5 months ago

Resolution: invalid
Status: newclosed

Feedback timeout. From the description it looks like a configuration and/or backend issue.

comment:3 by maxim, 4 months ago

Milestone: nginx-1.21.7

Ticket retargeted after milestone deleted

Note: See TracTickets for help on using tickets.