Unable to block post requests for qwant.com

[molytov]

I'm trying to block post requests with the following filters when using the qwant.com search engine:

||api.qwant.com/v3/suggest^$all
||www.qwant.com/action/ui^$all
||www.qwant.com/impression/qwant^$all
||www.qwant.com/action/display^$all
||mn.qwant.com/v2/api/feedback^$all

Although the first filter for search suggestions works to block requests, the others do not; the browser still keeps managing to make requests to them, and I can only block requests to them using the Firefox DevTools.
What am I missing?

[MasterKia]

No problems on my side.

What happens if you try to block the request using the uBO logger?
https://github.com/gorhill/uBlock/wiki/The-logger

By the way you don't need to use $all here, it's unnecessary. Just use ||api.qwant.com/v3/suggest^$xhr or even ||api.qwant.com/v3/suggest^.

[molytov]

For me, the Ublock - Ads filter has @@|| rules that allow those pings to be made. (in filters-2024.txt)

@@||qwant.com/apm/intake/v2/rum/events$xhr,1p
@@||qwant.com^$ping,1p

Disabling that filter list then allows the EasyPrivacy list to block them.

If I understand it correctly, the Ads list has exceptions set, which overrides any other filters that would otherwise block the pings.

I'm not sure why the ads filter would have exceptions for those, and I don't think it should. If it's to block ads, why shouldn't it also block this kind of telemetry stuff as well, or at least not include the exceptions that negate options set by other filters or the user themselves?

[uBlock-user]

@@||qwant.com/apm/intake/v2/rum/events$xhr,1p,badfilter
@@||qwant.com^$ping,1p,badfilter

[stephenhawk8054]

I'm not sure why the ads filter would have exceptions for those, and I don't think it should. If it's to block ads, why shouldn't it also block this kind of telemetry stuff as well, or at least not include the exceptions that negate options set by other filters or the user themselves?

You can read the reference issues threads few lines above: ! https://github.com/uBlockOrigin/uAssets/issues/22175. Usually all filters were added to resolve issues reported by other users. We don't add exceptions out of nowhere.

Whether the filters are obsolete or still needed depend on the websites' updates and users' reports.

[molytov]

I'm not sure why the ads filter would have exceptions for those, and I don't think it should. If it's to block ads, why shouldn't it also block this kind of telemetry stuff as well, or at least not include the exceptions that negate options set by other filters or the user themselves?

You can read the reference issues threads few lines above: ! https://github.com/uBlockOrigin/uAssets/issues/22175. Usually all filters were added to resolve issues reported by other users. We don't add exceptions out of nowhere.

Whether the filters are obsolete or still needed depend on the websites' updates and users' reports.

I see, thanks.
I'm not getting any adblock popups or warnings for now, so it's possible it's not needed anymore but I'll try using it for a little while.

[stephenhawk8054]

That issue thread has a label geo specific which means it only occurs on some regions / countries, and not everyone can reproduce the anti-adblock.