We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
During the integration of FETCH/ResourceTiming, some subtle changes were made. WPT needs to account for them.
fetchStart
startTime
transferSize
encodedBodySize + 300
0
nextHopProtocol
The text was updated successfully, but these errors were encountered:
@yoavweiss
Sorry, something went wrong.
Would it make sense for this issue to sit in the resource timing repo?
I don’t have a clear opinion on this... whatever is customary
The transferSize parts were covered as part of https://chromium-review.googlesource.com/c/chromium/src/+/2878693
No branches or pull requests
During the integration of FETCH/ResourceTiming, some subtle changes were made.
WPT needs to account for them.
fetchStart
andstartTime
when TAO-protected should not expose redirect timetransferSize
is alwaysencodedBodySize + 300
or0
(if cached). It shouldn't expose actual cookie value.nextHopProtocol
should be TAO protected: https://github.com/web-platform-tests/wpt/blob/master/resource-timing/nextHopProtocol-is-tao-protected.https.htmlThe text was updated successfully, but these errors were encountered: