Skip to content
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

Custom filtering rules not working correct #897

Closed
hdtvspace opened this issue Jul 22, 2019 · 2 comments
Closed

Custom filtering rules not working correct #897

hdtvspace opened this issue Jul 22, 2019 · 2 comments
Labels

Comments

@hdtvspace
Copy link

Custom rules
...
||stern.de/gujAd.js$match-case
||commsvc.stern.de^$important
||www.stern.de/gujAd.js$match-case
||commsvc.stern.de^
...

Adguard Home is not blocking the anti adblocker script from commsvc.stern.de or an simple ad script gujAd.js withe the custom rules above. Tried also 0.0.0.0 commsvc.stern.de. But the subdomain commsvc.stern.de is always loaded.

And the webmaster from stern has made a big mistake and delivers the script from a subdomain, easy to block. But adguard home is not blocking it.

Steps to reproduce

  1. Load the site www.stern.de, click and read an article and scroll down. Load the browser developer tools and the scripts are loaded.

Expected behavior

Customs riles are not applied

Actual behavior

The scripts are loaded. Also the safari browser cache is before loading the site cleared.

Screenshot:

Your environment

Description Value
Version of AdGuard Home server: (e.g. v1.0)
0.97.1
How did you setup DNS configuration: (System/Router/IoT)
Router
If it's a router or IoT, please write device model: (e.g. Raspberry Pi 3 Model B)
Raspberry Pi 3 Model B
Operating system and version: (e.g. Ubuntu 18.04.1)
raspian buster
@hdtvspace
Copy link
Author

So after an whole restart of the raspberry and the imac the ||commsvc.stern.de^ is working and blocked, but not rules with match-case e.g. ||stern.de/gujAd.js$match-case

The JS file is always loaded.

@ameshkov
Copy link
Member

DNS server operates with domains, not full URLs.

The only way to filter actual HTTP requests is to implement a proxy. Vote for this feature request if you'd like to have it: #391

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants