[Bug 23348] The loaded property doesn't make sense when the body is compressed

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23348

Boris Zbarsky <bzbarsky@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bzbarsky@mit.edu

--- Comment #6 from Boris Zbarsky <bzbarsky@mit.edu> ---
I think there is some confusion here.  In general, you start off with some data
(1).  Then you apply content-encodings to get a different set of data (2). 
Then you apply transfer-encodings to get a third set of data (3).

What's transferred over the network is (3): the RFC 2616 message-body.

The RFC 2616 entity-body is (2).  This is typically what Content-Length refers
to.

The data the application actually receives from the HTTP library in browsers is
typically (1).  That's certainly what happens in Gecko.

The current spec says to show the number of bytes of (2) that have been
transferred for "loaded", so the number will in some way correspond to "total".

Actual UAs simply don't have that information right now, so they're showing the
number of bytes the HTTP layer has handed them instead, which are bytes of (1),
not (2).

(In reply to Marcelo Volmaro from comment #2)
> I don't see how either, but it is what all browsers seems to do. Maybe they
> are all wrong. 

Per spec, yes they are.

This is not a spec/definition problem; it's a pure implementation problem as
far as I can tell.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 25 September 2013 16:31:06 UTC