Параметры adblock. Adblock plus – защита от всплывающих окон
This guide is designed to help you write and maintain your own Adblock Plus filters. Creating your own filters gives you more control over the things you want to see and don’t want to see on the websites that you visit, including ads, images, requests, and scripts.
Important
: All filter examples in this guide are only examples and are not meant to be used.
Table of contents
About Adblock Plus filters
The following filter lists come pre-installed with Adblock Plus:
Acceptable Ads
EasyList (+ bundled language filter list - depending on your browser’s language setting)
ABP Anti-circumvention filter list
In addition to these pre-installed filter lists, you can create your own filters. A filter is simply a rule that tells your browser which elements to block. A filter list is a set of rules that tells your browser what to block.
Creating filters
There are several types of filters, or filter rules, including:
Blocking filters
Applied on the network level to decide whether a request should be blocked.
Hiding filters
(oftentimes referred to as element hiding filters)
Hide particular elements on a page, including element hiding with extended selectors (emulation) as well as snippets.
Exception filters
Used to unblock certain requests or unhide certain elements on certain websites. Additionally, they can allow certain network requests despite filters that would otherwise block the requests.
Note
: Blocking and hiding filters can be set to negate or reverse the effects of other filters. These are then considered exception filters
.
You can easily create your filter(s) via the Adblock Plus Settings page.
Adblock Plus (version 3.4 and higher) for all browsers that support WebExtensions API like Chrome, Edge, Firefox, Opera and Yandex Browser:
Click the Adblock Plus
icon and then click the gear
icon in the upper-right corner.
The Adblock Plus Settings
tab opens.
Select the Advanced
tab and scroll to the Create and edit your filter list
section.
Click Start creating my filter list
.
Enter your filter and click Save
.
Basic filter rules
The most trivial filter you can define is the address of the request you want to block. However, this address often changes every time you open a page. For example, it could be http://example.com/ads/banner123.gif where 123 is a random number. Here, blocking the complete address won"t help. You’ll need a more general filter, like http://example.com/ads/banner*.gif , or even http://example.com/ads/ , which blocks everything in the “ads” directory.
Note
: Make sure that you don’t replace too much
with wildcards. The filter http://example.com/ will block all banners, but it’ll also block everything else from example.com that you still might want to see.
Defining exception rules
If you notice that your filter is blocking something it shouldn"t, you might consider using an exception rule rather than removing or matching the filter. Exception rules allow you to define cases where filters shouldn"t be applied. Exception rules are no different from filter rules; you can use wildcards or regular expressions.
Example
: If you are unhappy with your filter adv blocking http://example.com/advice.html , you can define an exception rule @@advice . You only need to precede it by @@ to indicate an exception rule.
Exception rules can do more, however. For example, if you specify $document option , you’ll get an exception for the entire page. If your exception rule is @@||example.com^$document and you open a page from example.com , Adblock Plus will be turned off on this page and nothing will be blocked.
Matching at the beginning or end of an address
Adblock Plus typically treats each filter as if it has a wildcard at its beginning and end (i.e. there’s no difference between the filters ad and *ad*). While this is usually unproblematic, sometimes you might want the filter you defined to only match at the beginning or the end of an address.
Example
: You want to block all Flash, but if you add the filter swf , the address http://example.com/swf/index.html is also blocked. The solution is to add a pipe symbol (|) to the filter to show that there should be a definite end at this point. For example, the filter swf| blocks http://example.com/annoyingflash.swf but not http://example.com/swf/index.html . And the filter |http://baddomain.example/ blocks http://baddomain.example/banner.gif but not http://gooddomain.example/analyze?http://baddomain.example .
You might want to block http://example.com/banner.gif as well as https://example.com/banner.gif and http://www.example.com/banner.gif . You can do this by putting two pipe symbols in front of the filter. This ensures that the filter matches at the beginning of the domain name: ||example.com/banner.gif , and blocks all of these addresses while not blocking http://badexample.com/banner.gif or http://gooddomain.example/analyze?http://example.com/banner.gif .
Marking separator characters
Sometimes, you might need to accept any separator character in a filter. For example, you might write a filter that blocks http://example.com/ and http://example.com:8000/ but not http://example.com.ar/ . Here, the symbol ^ can be used as a placeholder for a single separator character, http://example.com^ . The separator character can be anything but a letter, a digit, or one of the following: _ , - , . , % . The end of the address is also accepted as a separator.
In the following example, all separator characters are shown bolded in blue:
http:
//
example.com :
8000 /
foo.bar ?
a =
12 &
b =
%D1%82%D0%B5%D1%81%D1%82
This address can be blocked with the filters ^example.com^ or ^%D1%82%D0%B5%D1%81%D1%82^ or ^foo.bar^ .
Comments
Any rule that starts with an exclamation mark (!) is considered a comment. Adblock Plus ignores this rule for actual blocking, so it’s safe to write whatever you want in the comment. You can place a comment rule above a filter to describe its purpose or function, or you can place a comment above your filter list stating your authorship (most filter list authors do this).
Advanced features
Specifying filter options
Adblock Plus allows you to specify a number of options to modify the behavior of a filter. These options should be separated with a comma (,) after a dollar sign ($) at the end of the filter.
Example
: /ads/*$script,match-case
Here, /ads/* is the actual filter, and script and match-case are its options. Currently, the following options are supported:
Type options
These determine which types of elements a filter can block (or whitelist in case of an exception rule). Multiple type options can be specified to indicate that the filter should be applied to several types of elements. Possible types include:
Inverse type options
These specify which requesttypes the filter should not
be applied to. Possible inverse type options include ~script, ~image, ~stylesheet, ~object, ~xmlhttprequest, ~subdocument, ~ping, ~websocket, ~webrtc, ~document, ~elemhide, ~other
Restriction to third-party/first-party requests
If the third-party option is specified, the filter is only applied to requests from a different origin than the currently viewed page. Similarly, ~third-party restricts the filter to requests from the same origin as the currently viewed page.
Domain restrictions
The option domain=example.com means that the filter should only be applied on pages from the example.com domain. Multiple domains can be specified using | as the separator. For the option domain=example.com|example.net , the filter is only applied on pages from example.com or example.net domains. If a domain name is preceded with ~ , the filter should not
be applied on pages from this domain. For example, domain=~example.com means that the filter should be applied on pages from any domain but example.com and domain=example.com|~foo.example.com restricts the filter to the example.com domain with the exception of foo.example.com subdomain.
Sitekey restrictions
The option sitekey=abcdsitekeydcba means that the filter should only be applied on pages that provide a public key and a signature that can be verified by that very same public key that is also contained in the filter (but without the trailing =). Multiple sitekeys can be specified using | as a separator. For example, the option sitekey=abcdsitekeydcba|bcdesitekeyedcb only allows the filter to be applied on pages providing either sitekey abcdsitekeydcba or bcdesitekeyedcb . This is similar to domain restrictions, but allows for scenarios where a single filter should apply to a very large number of domains. Note
: Sitekey restrictions require .
Content Security Policies
The option csp=script-src: "none" causes a Content Security Policy header of script-src: "none" to be injected into HTTP responses for requested documents matching the filter (assuming that exception rules with the same option don"t also match and that the document isn’t whitelisted). The Content Security Policy script-src: "none" blocks all scripts, including inline, in the document. This filter option should generally be avoided, except as a last resort to counter advanced circumvention. (Adblock Plus 3.1 or higher is required.)
Redirecting requests to internal resources
The rewrite= option allows the rewriting of URLs (or redirecting requests) to an internal resource in order to deactivate it without causing an error. Indicate the internal resource by name and prefix abp-resource: in order to be recognized. For example $rewrite=abp-resource:blank-js sends an empty JavaScript. (Adblock Plus 3.5 or higher required.) Available internal resources are:
Any other value will make the filter have no effect and let the request pass through.
A few notes about using the rewrite option
Using regular expressions
Adblock Plus supports filters written in regular expressions (regex). For example, the filter /banner\d+/ matches banner123 and banner321 but not banners . We recommend checking out Mozilla’s documentation on regular expressions to learn how to write them.
Note
: For performance reasons, we recommend avoiding regular expressions if possible.
Special comments
Special comments only have an effect in downloaded filter lists, not in custom filters. They can set a number of parameters for the filter list:
! Homepage: http://example.com/ - This comment determines which webpage should be linked as filter list homepage.
! Title: FooList - This comment sets a fixed title for the filter list. If this comment is present, the user is no longer able to change the title.
! Expires: 5 days - This comment sets the update interval for the filter list. The value can be given in days (e.g. 5 days) or hours (e.g. 8 hours). Any value between 1 hour and 14 days is possible. Note that the update will not necessarily happen after this time interval. The actual update time is slightly randomized and depends on some additional factors to reduce server load.
! Redirect: http://example.com/list.txt - This comment indicates that the filter list has moved to a new download address. Adblock Plus ignores any file content beyond that comment and immediately tries downloading from the new address. In case of success, the address of the filter list is updated in the settings. This comment is ignored if the new address is the same as the current address, meaning that it can be used to enforce the "canonical" address of the filter list.
! Version: 1234 - This comment defines a numerical version of the filter list. This version number is displayed in issue reports and can be used to verify that the report refers to the current version of the filter list.
Element hiding
Basic rules
Unfortunately, there are some advertisements that can"t immediately be blocked. This is because they’re embedded as text in the webpage itself. If you look at the source code of the webpage, you might find something like this:
Cheapest tofu, only here and now!
Really cheap tofu, click here!
Only here you get the best tofu!
You’ll need to download the webpage in order to download the advertisements. After the webpage is downloaded, you can hide the advertisement(s) that you don’t want to see.
The example advertisement above is contained inside an element with the class attribute textad . The rule ##.textad hides any such element. Here ## marks an element hiding rule while the rest is a selector identifying the elements that need to be hidden. You can hide elements by their ID attribute (similarly, ###sponsorad hides the second advertisement) and by their name (e.g. ##textad for the third advertisement).
Limiting rules to certain domains
Typically, you may want to hide a specific ad on one site, but don"t want your rule to be applied to another site. For example, the rule ##.sponsor might hide valid code on some sites. But, if you write it as example.com##.sponsor , it will be applied on http://example.com/ and http://something.example.com/ , but not on http://example.org/ . You can also specify multiple domains by simply separating them with commas: domain1.example , domain2.example , domain3.example##.sponsor .
If a domain name is preceded with ~ , the rule is not
applied on pages from this domain. For example, ~example.com##.sponsor is applied on pages from any domain, but "example.com" and example.com,~foo.example.com##.sponsor make the rule apply on the "example.com" domain with the exception of the "foo.example.com" subdomain.
Note
: Because of how element hiding is implemented, you can limit it only to full domain names. You cannot use any other part of the address and you cannot use domain as a replacement for domain.example,domain.test .
Attribute selectors
Some advertisers don"t make it easy for you - their text advertisements have neither an ID nor a class attribute. You can use other attributes to hide those, for example ##table hides tables with a width attribute set to 80%. If you don"t want to specify the full value of the attribute, ##div hides all div elements with a title attribute containing the string "adv" . You can also check the beginning and the end of an attribute, for example ##div hides div elements with title starting with "adv" and ending with "ert" . As you see, you can also use multiple conditions - table matches tables with a width attribute set to 80% and bgcolor attribute set to white.
Advanced selectors
In general, any CSS selector supported by your browser can be used for element hiding. For example the following rule hides anything following a div element with class "adheader": ##.adheader + *. For a full list of CSS selectors, refer to W3C’s CSS selectors documentation . Please keep in mind that browsers are slower to process these types of selectors than selectors based on class or ID attribute only.
Note
: This functionality is recommended for advanced users. You should be comfortable with CSS selectors to use it. Adblock Plus won’t accept your custom filter if you use an invalid CSS syntax.
Extended CSS selectors (Adblock Plus-specific)
Sometimes the standard CSS selectors aren"t powerful enough to hide an advertisement. For those cases, we’ve added some new selectors, namely:
:-abp-has()
:-abp-contains()
:-abp-properties() (Adblock Plus 1.13.3 or higher for Chrome and Opera is required.)
When writing an element hiding filter that makes use of these extended selectors, you must use the #?# csyntax, e.g. example.com#?#selector . It"s important to note, however, that doing so creates a performance impact, so do so sparingly and make sure those filters are specific to as few domains and elements as possible.
:-abp-has()
The:-abp-has(selector) selector selects elements based on their content. For example, :-abp-has(> div > a.advertiser) selects elements that contain, as a direct descendant, a
