Opened on 07/02/2016 at 07:05:38 AM
Closed on 08/29/2019 at 05:48:47 PM
Last modified on 12/19/2019 at 05:09:54 PM
#4226 closed change (rejected)
provide a method to debug anti-adblocking (redirection)
| Reported by: | mapx | Assignee: | |
|---|---|---|---|
| Priority: | Unknown | Milestone: | |
| Module: | Platform | Keywords: | closed-in-favor-of-gitlab |
| Cc: | sebastian, kzar, greiner, arthur | Blocked By: | |
| Blocking: | Platform: | Chrome | |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by mapx)
ABP for chrome
Currently there is no possibility to debug (find necessary filters) the sites which detect the adblocking and which redirect themselves to some anti adblocking page.
It serves some global log(ger) - eventually enabled by some new option - which logs all the requests (and the triggered filters) for all the pages (even in the case of popunders).
For firefox exists "Diagnostics for Adblock Plus" addon which could be integrated in ABP (eventually see all the requests in the "blockable items list")
Example site (use only easylist)
http://www.aranzulla.it/
click some article and you'll be brought to a page like:
http://www.aranzulla.it/locked-chrome.gif.html?p=32372&caso=a&fabm=file&rnd=0.7277252475469795
Attachments (0)
Change History (6)
comment:2 Changed on 01/16/2017 at 10:45:56 AM by arthur
comment:3 Changed on 01/16/2017 at 12:09:15 PM by mapx
No, I didnt know (thanks), but it should be something integrated in ABP panel to be able to use all the features.
comment:4 Changed on 12/21/2017 at 11:27:49 AM by fhd
- Cc trev removed
comment:5 Changed on 08/29/2019 at 05:48:47 PM by sebastian
- Keywords closed-in-favor-of-gitlab added
- Resolution set to rejected
- Status changed from new to closed
Sorry, but we switched to GitLab. If this issue is still relevant, please file it again in the new issue tracker.
You probably know this already but you can check "Preserve log" in the Network panel so you can at least see what is getting blocked so the log isn't cleared after a reload or redirect.