Local Filtering tests will not expand

[erdoukki]

• [x] I am running the latest version
• [ ] I checked the documentation and found no answer
• [ ] I checked to make sure that this issue has not already been filed

Issue Details

• Version of AdGuard Home server:
  • v0.107.7
• How did you install AdGuard Home:
  • OpenWrt (do not remember, local script or package, but defaults upgraded from months)
• How did you setup DNS configuration:
  • Router + ADG
• If it's a router or IoT, please write device model:
  • GlobalScale / OpenWrt
• CPU architecture:
  • ARM64
• Operating system and version:
  • 19.x

Expected Behavior

When testing local filter, I would have get the answer about blocking status been more relevant.

Actual Behavior

When domain is checked in local filter status, if the domain is expandable (redirected) then the tests will only check the given text. It will not go through all different expandable possibles. It make difficult to find the status and the list. Only the Logs give the information.

Screenshots

Screenshot:

 

Additional Information

Issue already reported in a filtering list which make me have the issue

https://github.com/alexsannikov/adguardhome-filters/issues/7

THX

[EugeneOne1]

@erdoukki, hello, and thanks for the report. I'd say it's an expected behavior. The thing is the real request is blocked because of aushafeeds.b-cdn.net. canonical name in the response, which matches the rule. However, there are no DNS requests performed during the filtering check so there is no way to tell if the real request will be blocked until you made it yourself.

Actually, we already have a feature request (#4036) about enhancing the filtering check, so I think we can deal with performing the real request in the improved implementation.

[erdoukki]

Sure, it will be great to enhance the test for a dns like call. Thanks for feedback.