mirror of
https://github.com/gorhill/uBlock.git
synced 2024-11-16 23:42:39 +01:00
Expand description of redirect-rule
parent
5abe58d33f
commit
8253165d64
@ -234,7 +234,17 @@ A source hostname should always be specified, so the `domain=` option is strongl
|
|||||||
|
|
||||||
#### `redirect-rule`
|
#### `redirect-rule`
|
||||||
|
|
||||||
The purpose of this option is to add the ability to create standalone [`redirect`](#redirect) rule without being forced to create a block filter (a corresponding block filter is always created when using the `redirect=`).
|
Allows to create standalone [`redirect`](#redirect) rule without being forced to create blocking filter.
|
||||||
|
|
||||||
|
For example, consider the following filter:
|
||||||
|
|
||||||
|
`||example.com/ads.js$script,redirect=noop.js`
|
||||||
|
|
||||||
|
The above filter will result in a block filter ||example.com/ads.js$script **and** a matching redirect directive. Now consider this following filter:
|
||||||
|
|
||||||
|
`||example.com/ads.js$script,redirect-rule=noop.js`
|
||||||
|
|
||||||
|
The above filter will not cause a block filter to be created, only a redirect directive will be created. Standalone redirect directives are useful when the blocking of a resource is optional but we still want the resource to be redirected should it ever be blocked by whatever mean - whether through a separate block filter, a dynamic filtering rule, etc.
|
||||||
|
|
||||||
#### `xhr`
|
#### `xhr`
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user