Please check the user manual first (EN/DE) and find the knowledge base and answers to technical questions in the FAQs of the former eBlocker GmbH. Mac and iOS users please read this article in case of certificate issues.
Please post here ONLY if you found an issue that can be reproduced and did not exist in eOS 2.4.x
If you have other questions regarding eBlocker usage or you are not sure if it‘s a bug please open a NEW topic.
Posts to this thread will be deleted if they are not on topic.
THX!
Statistics display in dashboard can differ from display of blocked requests in controlbar.
To reproduce. Reset device statistics in dashboard. Visit faz.de. Blocker shows 1 but dashboard several blocked domains. (Thanks to @ulmisch for this find!)
Similar with computerbild.de 13 blocked requests, sum of blocked requests in stats is 13 as well but it reads 25 domains where (if you count all domians) sum is 9.
Might have been an issue in previous versions already.
@ulmisch From the machine deck - first analysis from @bpr :
I took a look at the faz page in the web inspector. The browser first gets a redirect to
https://www.faz.net/aktuell/
For 3rd party requests the browser only sends https://www.faz.net/ as referrer. Therefore the eBlocker can block these requests (and they appear in the statistics), but it cannot assign them to the current page because the path is missing.
The behavior is probably the same as the HTTP header "Referrer-Policy: origin-when-cross-origin" according to the documentation:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
The faz page does not set this header, but you can do it dynamically for individual resources. I haven't found where exactly this happens.
Interestingly, only one request can be assigned by the controlbar: advertisement from static.faz.net. The complete referrer is transferred there.
Now what that means is
- All trackers & such got blocked
- Due to a website controlled parameter eBlocker might show less blocked trackers in icon than it actually had blocked
- There might be no fix as this a security measure in the http protocol (we‘ll see 😉 )