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

Revert b1c1cdfbaf7e7adcb872857bb809a56e7acef089...baabca8c52a33b4c5277a8b930c3ba088b5b7dc2

gwarser 2018-01-29 13:12:37 +01:00
parent baabca8c52
commit a96fb5885d
1 changed files with 33 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
Strict-blocking.md Normal file

@ -0,0 +1,33 @@
[Back to Wiki home](https://github.com/gorhill/uBlock/wiki)
***
In uBlock Origin ("uBO"), _strict blocking_ is the blocking of a whole page, i.e. the _root_ document is blocked, so that not a single connection is made to the remote server hosting the web page.
By default, strict blocking is enabled in uBO (this is the opposite of Adblock Plus).
Adblock Plus only blocks secondary resources (see [web pages _themselves_ are **never** filtered](https://adblockplus.org/forum/viewtopic.php?t=18774#p85439)).
So if you were to create a filter such as `||example.com^`, and then navigate to <https://example.com>, Adblock Plus would not prevent you from connecting and loading the web page itself served at `https://example.com`, though all secondary resources pulled by that web page would be subject to filtering.
uBO respected that semantic until version 0.9.3.0. With version 0.9.3.0, uBO will subject web pages themselves to filtering.
This means that using the same test case above, **uBO will block the web page** served by a server found in one of the malware list (unlike Adblock Plus):
![Page was fully blocked](https://cloud.githubusercontent.com/assets/585534/8160013/14466ca0-133a-11e5-8d3c-28169288f35a.png)
Why the change? Because [issue #1013](https://github.com/chrisaljoudi/uBlock/issues/1013) brought forth why it is desirable sometimes to completely block a web site, as opposed to what the ABP-filtering semantic dictates.
In the end, the chosen solution is to now have web page themselves subject to filtering, just like all secondary resources.
In the figure above, the user will be given the choice to go back by closing the window or proceed to the web page by disabling strict blocking by selecting either:
- Temporarily - The site will be temporarily allowed for a limited time (currently set at 60 seconds).
- Permanently - The site will be permanently allowed.
This will prevent the web page _proper_ for the site from being blocked by uBO in the future: the filtering of the site will be done exactly as per ABP-filtering semantic, and just like with uBO pre-0.9.3.0.
There are many benefits to strict blocking. For example, there is no good reason one should want to connect _at all_ to any of the sites present in any one of the malware domain lists. Strict blocking will prevent this from happening.
**Important note:** Keep in mind that when the above warning occurs, it doesn't necessarily mean the site is harmful, it just means that there is a matching filter in the selected filter lists. You decide whether the site is safe, and whether disabling strict blocking permanently for the site is appropriate.
**Tip:** If you wish, you may entirely disable strict blocking everywhere by adding the rule `no-strict-blocking: * true` to the _My rules_ pane in the dashboard (don't forget to click _Commit_ to make the rule stick).