Work a transparent size example
Imagine a hypothetical playlist whose decoded text is 40,000 bytes and whose compressed response body is 10,000 bytes. The compression ratio by this simple body-size comparison is four to one. The application can read 40,000 bytes of text after receiving a 10,000-byte encoded body.
That difference is not evidence that the server omitted thirty thousand bytes. It reflects an encoding layer. Nor is the compression format the programme's video codec: a compressed text manifest and encoded video samples are different resources with different processing.
Keep headers and metric definitions
Content-Encoding can identify the additional HTTP coding. Browser performance entries distinguish encoded and decoded body sizes, while a complete transfer metric can also account for other response information under its definition. Do not label all these counters file size without qualification.
A body-size comparison also needs the same resource edition. Comparing yesterday's uncompressed list with today's differently populated compressed list combines content change and compression. Keep the validator or content relationship when measuring the encoding effect, rather than attributing every size difference to a changed server setting.
Use the distinction in a support report
If parsing fails, determine whether decoding the HTTP representation succeeded before examining playlist syntax. A correctly decoded body still needs to be valid media text. Conversely, a wrong Content-Encoding declaration can prevent the application from reaching that text at all.
For an authorised report, retain the content type, content encoding, relevant size definitions and error stage. Avoid posting private playlist contents. The calculation supports a clear explanation of one resource transfer; it does not establish total session data consumption, video quality or a universal compression saving for all channels and programmes. Use actual traffic records for a measured data-use claim.
Questions about this guide
Is decoded text size the same as transferred encoded body size?
Not necessarily. HTTP compression can make them differ.
Is gzip the video codec?
No. It can encode the text response for transfer; the media codec is another layer.