From ab65206339cecbc4d947a64b9f4bb4e1b3900573 Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 8 Oct 2017 09:16:34 -0400 Subject: [PATCH] Updated Static filter syntax (markdown) --- Static-filter-syntax.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Static-filter-syntax.md b/Static-filter-syntax.md index 36efb81..f03a59d 100644 --- a/Static-filter-syntax.md +++ b/Static-filter-syntax.md @@ -71,7 +71,9 @@ The filter syntax for `redirect=` filter option is a subset of ABP-compatible fi ||example.com/path/to/image$image,redirect=2x2-transparent.png,domain=github.com */$script,redirect=noopjs,first-party -Specifically, notice that the filter **must** start with `||` or `*`, otherwise no redirection directive will be created, though a blocking filter will be created. Essentially, a redirection filter must always have a destination hostname specified, or `*` if the filter is to apply to all destinations. A source hostname should always be specified, so the `domain=` option is strongly recommended. It is allowed to use `first-party` instead of `domain=`, in which case the source hostname will be that of the destination hostname. +Specifically, notice that the filter **must** start with `||` or `*`, otherwise no redirection directive will be created, though a blocking filter will be created. Essentially, a redirection filter must always have a destination hostname specified, or `*` if the filter is to apply to all destinations. + +A source hostname should always be specified, so the `domain=` option is strongly recommended. It is allowed to use `first-party` instead of `domain=[...]`, in which case the source hostname will be that of the destination hostname. ### Cosmetic filters