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

ResourceTiming - deliveryType #824

Open
jeremyroman opened this issue Jun 13, 2023 · 3 comments
Open

ResourceTiming - deliveryType #824

jeremyroman opened this issue Jun 13, 2023 · 3 comments

Comments

@jeremyroman
Copy link

Request for Mozilla Position on an Emerging Web Specification

Other information

The Resource Timing text currently only covers "" and "cache".

Chromium also implements "navigational-prefetch" as part of https://wicg.github.io/nav-speculation/prefetch.html (currently behind a flag). Some of that work might be covered by #620.

@zcorpan
Copy link
Member

zcorpan commented Jun 16, 2023

cc @bdekoz @bgrins

@smaug----
Copy link
Collaborator

How is this not revealing something new about user's browsing behavior, in other words, why is this not a privacy issue?

@jeremyroman
Copy link
Author

In the case of "cache", it is subject to whatever cache partitioning scheme the UA uses (e.g., if the cache is partitioned by top-level site, it doesn't reveal anything about browsing on other sites). Additionally, this is subject to the same protections as transferSize, which exposes the cache mode (0 implies local, 300 implies validated, any value above 300 implies uncached). transferSize and deliveryType are also subject to the same Timing-Allow-Origin check.

In the case of prefetch, browsers already send request headers indicating that a request is for prefetch, and servers could modify their response depending on this header.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Unscreened
Development

No branches or pull requests

3 participants