- From: <bugzilla@jessica.w3.org>
- Date: Wed, 25 Sep 2013 17:52:31 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23348 --- Comment #9 from Boris Zbarsky <bzbarsky@mit.edu> --- Marcelo, you're still being confused, I think. There are _two_ kinds of HTTP "compression". One (Content-Encoding) affects Content-Length. One (Transfer-Encoding) does not. The entity-body is the data after Content-Encoding but before Transfer-Encoding; the Content-Length is by definition the length of the entity-body in HTTP. The message-body, which is what Transfer-Encoding produces, is a transient phenomenon that can be changed in transit (e.g. a proxy is allowed to change the Transfer-Encoding, but not the Content-Encoding). Note that Transfer-Encoding can make the message bigger as well as smaller (e.g. see "chunked" Transfer-Encoding). Which is why in practice no one should be caring about the message-body. The XMLHttpRequest spec currently calls for both "total" and "loaded" to reflect the data after Content-Encoding but before Transfer-Encoding. Browsers currently show "total" per the spec, but "loaded" after undoing Content-Encoding. As in, they're not doing what the spec says. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 25 September 2013 17:52:32 UTC