You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Incorrect usage of |, || is not detected, for example - |||
Invalid rules |||example.com^ - should be || https://example.com/ads.js|| - should be | at the end
Redundant characters
||example.com/ads**.js|| - one * is enough, **+ - redundant
||*/banners/*$domain=example.com - ||* / |* at the beginning of non-domain like of URL part. In this example one * is required to make the rule non-regexp style (usually at the end).
The text was updated successfully, but these errors were encountered:
@ameshkov@maximtop In the longer term, perhaps we should parse the network rule patterns. Thus, using || incorrectly or using a space/invalid chars within the pattern would result a syntax error. Moreover, the pattern could be fragmented, e.g. like this: ||example.com/*.js^ -> ['||', 'example.com/', '*', '.js', '^']
Incorrect usage of
|
,||
is not detected, for example -|||
Invalid rules
|||example.com^
- should be||
https://example.com/ads.js||
- should be|
at the endRedundant characters
||example.com/ads**.js||
- one*
is enough,**+
- redundant||*/banners/*$domain=example.com
-||*
/|*
at the beginning of non-domain like of URL part. In this example one*
is required to make the rule non-regexp style (usually at the end).The text was updated successfully, but these errors were encountered: