Mirrors
/
uBlock
mirror of https://github.com/gorhill/uBlock.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Three minor grammar edits.

Brian Zelip 2017-12-30 10:39:32 -05:00
parent 6ac12751b4
commit 98b015c101
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Disable-hyperlink-auditing-beacon.md

@ -4,10 +4,10 @@ See [_"Hyperlink-Auditing aka `<a ping>` and Beacon aka `navigator.sendBeacon()`
### Chromium-based browsers ### 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. For those browsers, the network requests fired as a result of calling `navigator.sendBeacon()` are sent 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 #### 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. 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 requests 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. The [webRequest API](https://developer.chrome.com/extensions/webRequest) was extended in Chromium 49 to support new request types, and thus the setting 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.