From d0d3a6fbf4ef05322a1023fd9627b4cb95fcd90e Mon Sep 17 00:00:00 2001 From: Santiago Quintero Date: Thu, 7 Dec 2017 17:27:31 +0100 Subject: [PATCH] Revert e84de8a22413b6b90fe9e9c6ac35de9a00fe799b...8260d9eb85c5876a654cfc674b6cd35b1dfcc14e on Disable hyperlink auditing beacon --- Disable-hyperlink-auditing-beacon.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/Disable-hyperlink-auditing-beacon.md b/Disable-hyperlink-auditing-beacon.md index 0e5f257..908607a 100644 --- a/Disable-hyperlink-auditing-beacon.md +++ b/Disable-hyperlink-auditing-beacon.md @@ -1 +1,13 @@ -hahahaha \ No newline at end of file +### Background information + +See [_"Hyperlink-Auditing aka `` and Beacon aka `navigator.sendBeacon()`"_](http://www.wilderssecurity.com/threads/hyperlink-auditing-aka-a-ping-and-beacon-aka-navigator-sendbeacon.364904/). + +### Chromium-based browsers + +For those browsers, the network requests fired as a result of calling `navigator.sendBeacon()` are send as [behind-the-scene](https://github.com/gorhill/uBlock/wiki/Behind-the-scene-network-requests) network requests. + +#### Caveats for browsers based on Chromium version 48 or less + +Network requests created as a result of web pages using `navigator.sendBeacon()` **will not be blocked** when the setting _"Disable hyperlink auditing/beacon"_ is checked. This is a limitation of the chrome API prior to v49, as network request fired as a result of calling `navigator.sendBeacon()` are reported as the generic type `other` by the browser. + +The [webRequest API](https://developer.chrome.com/extensions/webRequest) was extended in Chromium 49 to support new request types, and thus the settings works fine for any browser based on Chromium 49 or higher, as there is now a specific network request type, `ping`, which uBO normalizes to `beacon` -- and hence can now filter correctly. \ No newline at end of file