-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Regression] domain=
option fails to match in some rare cases
#3328
Comments
Good catch, thanks for reporting. Regression from 5928996. |
To assess severity, I looked a bit in EasyList to find out if any existing filters would suffer the issue here, and I suspect there might be no case of filters being affected. Normally a filter such as:
Would be really written as
Because there is no point specifying |
I see, but filter maintainers modify old filters, add exceptions so, probably, it turned out with this filter
From RU AdList: BitBlock Requests with |
domain=
option fails to match in some rare cases
Add this filter and go https://www.kaspersky.com/blog/
/jquery.smartbanner.$domain=~blog.kaspersky.com|~kaspersky.com
Exception
|~kaspersky.com
does not work. Requests with/jquery.smartbanner.
are bloked on kaspersky.comBut if you change the order, exception works ok. With this filter
/jquery.smartbanner.$domain=~kaspersky.com|~blog.kaspersky.com
Requests with
/jquery.smartbanner.
are not filteredThe text was updated successfully, but these errors were encountered: