Same cached objects, but different body_bytes_sent

Zhang Chao zchao1995 at gmail.com
Fri Jun 2 06:45:22 UTC 2017


Hi!

Are you sure the client didn't close the connection when the body is
transferring?


On 2 June 2017 at 10:00:36, Guilherme (guilherme.e at gmail.com) wrote:

I identified a strange behavior in my nginx/1.11.2. Same cached objects are
returning different content length. In the logs below, body_bytes_sent
changes intermittently between 215 and 3782 bytes. The correct length is
3782. (these objects are not being updated in this interval)

xxxxxxxxxx - - [02/Jun/2017:01:29:06 +0000] "GET
/img/app/bt_google_play.png HTTP/2.0" 200 *215* "xxxxxxxxxx" "Mozilla/5.0
(Linux; Android 6.0.1; SM-G600FY Build/MMB29M) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/58.0.3029.83 Mobile Safari/537.36" 42 215 10.571
"image/png" HIT
xxxxxxxxxx - - [02/Jun/2017:01:29:50 +0000] "GET
/img/app/bt_google_play.png HTTP/2.0" 200 *3782* "xxxxxxxxxx" "Mozilla/5.0
(iPhone; CPU iPhone OS 10_3_2 like Mac OS X) AppleWebKit/603.2.4 (KHTML,
like Gecko) Version/10.0 Mobile/14F89 Safari/602.1" 32 3791 0.344
"image/png" HIT

** request_time is always high for the shorter requests*

I'm ignoring Vary header in proxy_ignore_headers too.

Any idea about this?

Tks,

Guilherme
_______________________________________________
nginx mailing list
nginx at nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20170601/2c06163c/attachment.html>


More information about the nginx mailing list