AdguardForWindows
AdguardForWindows copied to clipboard
AdguardTeam
Connections are not filtered on `bilibili.com`
AdGuard version
7.12
Browser version
Chrome 111.0.5563.147
OS version
Windows 10
What filters do you have enabled?
AdGuard Base filter, AdGuard Chinese filter, AdGuard Tracking Protection filter, AdGuard URL Tracking filter, AdGuard Social Media filter, AdGuard Annoyances filter
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
What AdGuard gets is not an https connection but a tcp connection, so the path cannot be obtained. But the browser extension can get the path and match the rule.
Expected Behavior
Can get the path of all connections.
Screenshots
Additional Information
No response
@Karmylr Hey, can you tell the website you're having trouble with?
https://www.bilibili.com/
This is a normal behavior cause these requests(tcp) are not filtered.
But such connections that should be filtered are not filtered. That is to say, AdGuard For Windows cannot do the detailed filtering like browser extensions?
@Karmylr, hi, sorry for the late response. It seems the problem is not reproducing in the latest nightly version; at least, I observe blocked requests to data.bilibili in the filtering log. Could you please confirm on your side?
I was able to reproduce in 7.17.0 nightly 25. Maybe this is an expected behavior. Can you explain why some connections cannot get the path, but only the domain name?
If I understood you correctly and judging by your screenshot, you mean log records with the type Connection. Those entries represent connections, and they indeed only have domain names, as do log records of DNS type. Adguard extension doesn't have the log records of types Connection and DNS, and therefore doesn't have these "only domain name" records.