Skip to content
New issue

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

User Agent may want to restrict cross-origin transferSize/encodedBodySize/decodedBodySize visibility even with TAO #342

Closed
achristensen07 opened this issue Aug 27, 2022 · 2 comments · Fixed by #369

Comments

@achristensen07
Copy link
Contributor

Doing so would prevent a side-channel to gather data even from origins that send TAO headers. Similar to w3c/server-timing#89 which proposes a similar restriction for Server Timing.

@yoavweiss
Copy link
Contributor

This was discussed at TPAC, and there was agreement we can allow such UA liberties in the spec.

@achristensen07 - Are you interested in submitting a PR to that effect?

@achristensen07
Copy link
Contributor Author

I can make a PR

achristensen07 added a commit to achristensen07/resource-timing that referenced this issue Jan 26, 2023
even with the presence of TAO header fields.  This resolves
w3c#342
achristensen07 added a commit to achristensen07/resource-timing that referenced this issue Jan 26, 2023
even with the presence of TAO header fields.  This resolves
w3c#342
yoavweiss pushed a commit that referenced this issue Mar 3, 2023
even with the presence of TAO header fields.  This resolves
#342
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants