From 6818cc75dd756a664625cfba14fe2700e0b1d683 Mon Sep 17 00:00:00 2001 From: Ainar Garipov Date: Wed, 31 Aug 2022 14:57:07 +0300 Subject: [PATCH] Pull request: 4881-hosts-no-mods Updates AdguardTeam/AdGuardHome#4881. Squashed commit of the following: commit 9a1837046bb556456efa774f06c669303f1ad64f Author: Ainar Garipov Date: Wed Aug 31 14:52:12 2022 +0300 Hosts-Blocklists: clarify that hosts rules do not support modifiers --- Hosts-Blocklists.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/Hosts-Blocklists.md b/Hosts-Blocklists.md index 40af232..7491c71 100644 --- a/Hosts-Blocklists.md +++ b/Hosts-Blocklists.md @@ -174,6 +174,10 @@ You can change the behavior of a rule by adding modifiers. Modifiers must be located at the end of the rule after the `$` character and be separated by commas. +**NOTE:** Modifiers don't work with `/etc/hosts`-style rules. For example, +`127.0.0.1 example.org$badfilter` will **not** disable the original `127.0.0.1 +example.org` rule. + Examples: * ```none @@ -533,10 +537,6 @@ Examples: * `@@||example.org^$badfilter` disables `@@||example.org^`. -**NOTE:** The `badfilter` modifier currently doesn't work with -`/etc/hosts`-style rules. `127.0.0.1 example.org$badfilter` will **not** -disable the original `127.0.0.1 example.org` rule. - #### `ctag` The `ctag` modifier allows to block domains only for specific types of DNS @@ -616,7 +616,8 @@ IP_address canonical_hostname [aliases...] Fields of the entries are separated by any number of space or tab characters. Text from the `#` character until the end of the line is a comment and is -ignored. +ignored. Modifiers, such as `client` or `badfilter`, don't work with these +rules. Hostnames may contain only alphanumeric characters, hyphen-minus signs (`-`), and periods (`.`). They must begin with an alphabetic character and end with an