http stats and unrealistic "request size" results

from bigpipe shell

 

 

bp> http stats reset

 

 

count to 30

 

 

bp> http stats show

 

...

 

| response size ( <1k, 1-4k, 4-16k, 16-32k, 32-64k, 64-128k, 128-512k, 512k-2M, >2M)

 

| (12613, 29018, 1877, 38, 198, 13, 13, 1, 170636)

 

...

 

 

this is simply not possible. the vast majority of our response payload is under 32K, in fact i could not think of any responses that our site generates which are that big.

 

 

is it possible that anything without a Content-Length: header gets lumped into that >2M bucket? if not, what else could be causing this discrepancy?

 

 

thanks!