-
Notifications
You must be signed in to change notification settings - Fork 22
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
privacy and security considerations #2
Comments
/cc @mikewest for a sanity check
No, as that would break the primary analytics use case. That said, you can limit this behavior via CSP connect-src.
Yes, many analytics use cases rely on cookies.
CSP The preflight due to Beacon-Age is a good catch. I'd be great to exempt it, if possible. |
Added privacy section as requested. Please take a look. |
Following the thread at
http://lists.w3.org/Archives/Public/public-web-perf/2014Jul/0109.html
It seems to me that the security and privacy considerations should say that Beacon doesn't add extra security and privacy considerations in addition to the ones associated with form submissions in HTML. It should point to http://www.w3.org/TR/html5/introduction.html#fingerprint .
The text was updated successfully, but these errors were encountered: