[Webkit-unassigned] [Bug 273818] PerformanceNavigationTiming decodedBodySize larger than encodedBodySize if resource is not encoded

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=273818

--- Comment #2 from Gernot Raudner <gernot.raudner at dynatrace.com> ---
Maybe my example was bad, or this is a separate issue, not sure... I also have a webserver that doesn't support HTTP/2, and the difference is, interestingly enough, 18 bytes (35910 compressed versus 35892 decompressed).

It doesn't really solve my issue either, because I compare the data I generate on the server with the data I receive on the client, and even though the body matches, as well as the encodedBodySize (of course, since it's not encoded), but the decodedBodySize is invalid. I don't really see how this is arguably correct in the context of the Performance API. It might be correct in the context of HTTP frames, but this shouldn't be linked to the Performance API, should it?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240508/66fa5b3d/attachment.htm>