From 52dd4ffacfad5e1e456008c72e788a7c58bf7e00 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Tue, 9 Jun 2015 11:18:08 -0400 Subject: [PATCH] Now unsure whether this was a case of send beacon, need to investigate more thoroughly --- Dashboard:-Settings.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/Dashboard:-Settings.md b/Dashboard:-Settings.md index cfdce28..eaea089 100644 --- a/Dashboard:-Settings.md +++ b/Dashboard:-Settings.md @@ -36,8 +36,6 @@ Google's [_"Make webpages load faster"_](https://support.google.com/chrome/answe Checking this will prevent hyperlink auditing/beacon[1]. _Hyperlink auditing_ and _Send beacon_ are best summarized as "phone home" features (or even "phone anywhere"). The details are well explained [here](http://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/). -![Figure 2](https://cloud.githubusercontent.com/assets/585534/8056381/92121158-0e75-11e5-951d-43424e416959.png)
"Send beacon" in action: a behind-the-scene network request sent to 3rd-party `linkedin.com` **after** leaving [this page](http://www.eetimes.com/document.asp?doc_id=1326794) on `eetimes.com`. - **[1] Important note:** _"Send beacon"_ can not be disabled in Chromium. Advanced users can filter behind-the-scene network requests, where the beacon-related network requests show up. #### Backup/restore section