making custom filter rule protocol indepent

[eddydc]

Hi,
I wanted to block a domain and followed the example
||example.org^ – block access to the example.org domain and all its subdomains

After implementation, https://example.org isn't blocked. What should I do that everything for that domain gets blocked?
Cheers,
Eddy

[ameshkov]

This rule of yours blocks example.org. If it's not blocked in your browser, maybe the problem is with how your devices are configured. Maybe they're not using AGH for instance.

[ameshkov]

The test option accepts domain names, not URLs. The fact that it accepted http://example.org is a mistake.

[eddydc]

OK I understand that the test should only test domains independent from the protocol and the interface is incorrect concerning this. But I encountered several times the issue that https:// isn't blocked and shown on the device despite that AGH is the only DNS server specified.

[eddydc]

I've been testing on two machines. One connected to adguard only and one to pihole only. Both are set with the custom blocking rules in their respective formats. Whereas pihole does block the desired domains, AGH doesn't. I thought it was protocol dependent, but that's not the case. So as far I am concerned, it's a bug.

[ameshkov]

I am not sure how exactly you're testing, but ||example.org^ blocks example.org regardless of the protocol (DNS knows nothing about protocols anyway).

You may want to use nslookup to test this.

[eddydc]

It seems that the browser is the culprit. After clearing all caches, things work as expected