[resource-timing] Add a test for encodedBodySize with no Content-Length header #27952
Labels
Comments
noamr
added a commit
that referenced
this issue
Mar 9, 2021
Added tests for different scenarios of `Content-Length` header and how it affects `encodedBodySize`. Closes #27952
noamr
added a commit
that referenced
this issue
Mar 9, 2021
Added tests for different scenarios of `Content-Length` header and how it affects `encodedBodySize`. Closes #27952
noamr
added a commit
that referenced
this issue
Mar 10, 2021
Added tests for different scenarios of `Content-Length` header and how it affects `encodedBodySize`. Closes #27952
noamr
added a commit
that referenced
this issue
Mar 10, 2021
Added tests for different scenarios of `Content-Length` header and how it affects `encodedBodySize`. Closes #27952
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this issue
Mar 19, 2021
…BodySize, a=testonly Automatic update from web-platform-tests [Resource-Timing] content-length/encodedBodySize (#27955) Added tests for different scenarios of `Content-Length` header and how it affects `encodedBodySize`. Closes web-platform-tests/wpt#27952 -- wpt-commits: a0c6344f36cf8079943523314cfeac959e24dea3 wpt-pr: 27955
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to the resource timing spec,
encodedBodySizeshould return the actual size of the body, and not rely on theContent-Lengthheader. But there is no test to that effect, as all the tests rely on static resources.There should be a test that ensures the correct
encodedBodySizefor this case.https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-encodedbodysize
See whatwg/fetch#1185
The text was updated successfully, but these errors were encountered: