Reliably track request and response content length

[a1exsh]

Some user agents set the Content-Length header, but not all. Use request and response wrapper class together with counting input/output stream wrappers.

[antban]

the PR is transforming from counting actual values (compressed bytes) to non-compressed, is it the intention?

[a1exsh]

the PR is transforming from counting actual values (compressed bytes) to non-compressed, is it the intention?

It is not intentional, but I thought it might be useful to measure both compressed and original size of both request and response. Btw, it doesn't look like we support zstd compression for response — only for request.

[antban]

@a1exsh yes, zstd response compression is not supported

[a1exsh]

@antban Counting actual bytes on the uncompressed stream is the only reliable way to do it on this level, as the Content-Length header is only set by some of the user agents (and they are not required to set it anyway). If we want to track compressed sizes as well, we should be doing that on the compression filter level.

[adyach]

👍

[antban]

:+1:

[a1exsh]

:+1:

[antban]

:+1:

[a1exsh]

:+1:

[antban]

:+1: