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

Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy (w3c/resource-timing #221) #39

Open
kdzwinel opened this issue Feb 5, 2020 · 0 comments
Assignees
Labels
needs-resolution PING expects this item to be resolved to their satisfaction. s:resource-timing https://w3c.github.io/resource-timing/ wg:webperf https://www.w3.org/groups/wg/webperf

Comments

@kdzwinel
Copy link

kdzwinel commented Feb 5, 2020

This is a tracker issue. Only discuss things here if they are PING internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ w3c/resource-timing#221

@plehegar plehegar added tracker PING is following a discussion, but doesn't require resolution. s:resource-timing https://w3c.github.io/resource-timing/ labels Feb 11, 2020
@samuelweiler samuelweiler added needs-resolution PING expects this item to be resolved to their satisfaction. and removed tracker PING is following a discussion, but doesn't require resolution. labels Jul 1, 2021
@w3cbot w3cbot added the wg:webperf https://www.w3.org/groups/wg/webperf label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-resolution PING expects this item to be resolved to their satisfaction. s:resource-timing https://w3c.github.io/resource-timing/ wg:webperf https://www.w3.org/groups/wg/webperf
Projects
None yet
Development

No branches or pull requests

4 participants