Open MysticalCreation opened 1 year ago
Confirmed. :thumbsup:
Indeed, I spotted this problem too (a report was planned for later in my todo list).
But in my case, not by setting Site access
value to On specific sites
(although also confirmed) but to On click
.
💭 Since logically the extension is limited at the browser level by this set value, there is a good chance that it is not solvable I think (not sure at all however, luckily there is a solution). But anyway, if the extension can manage to determine when this case is encountered, a more explanatory notification might be nice at least. Or else, possibly add details about that in the KB, possibly in a new Specific cases section.
Hi, thanks for workaround but unfortunately it's not working still. I did what you said and added domain names in the allowlist and still get the error.
but still get the error-
Also ublock origin doesn't have this issue of updating filters even on limited website access permissions so I'm confused why it might not be possible in adguard. This feels like a bug and not a limitation of the browser.
Firstly, it's not the "Allowlist" of AdGuard but the one in Edge's extension details (see this screenshot again).
Secondly, URL format will be https://easylist-downloads.adblockplus.org/*
(and not https://easylist-downloads.adblockplus.org/antiadblockfilters.txt/*
). (And small note: /*
will be auto. added by Edge if omitted.)
Thirdly, after verification, all filters natively included in AdGuard, even 3rd-party ones, go through filters.adtidy.org
in fact (I updated my post, sorry about that so). Therefore, only the domain names of your possible "Custom filters" (if used) are to be added in addition to https://filters.adtidy.org/*
.
1) Go to AdGuard extension details in Edge.
**Direct URL access:**
if installed via the Chrome Web Store ››› `edge://extensions/?id=bgnkhhnnamicmpeenaelnjfhikgbkllg`
if installed via the Microsoft Edge Add-ons Store ››› `edge://extensions/?id=pdffkfellgipmhklpdmokmckkkfcopbh`
2) Click this "Add" button and add just these 3 ones:
https://filters.adtidy.org/*
https://gitlab.com/*
https://big.oisd.nl/*
So, in your specific case (based on your screenshot):
- Go to URL
edge://extensions/?id=bgnkhhnnamicmpeenaelnjfhikgbkllg
(or manually go to AdGuard extension details in Edge);- Click this "Add" button and add just these 3 ones:
https://filters.adtidy.org/*
https://gitlab.com/*
https://big.oisd.nl/*
And don't forget to remove the wrongly added things from your AdGuard's Allowlist of course. 😉
thank u so much. This works. Hopefully a proper fix is released soon.
@contribucious I just have one unrelated query hopefully you can answer it since you're here. I always wondered that extensions said that they have permission to read all websites data. Does setting the permission to "specific sites" or "on click" take away that permission since the text indicating that the permission still has complete website data access is still there?
According to me, but I could be wrong, Edge just reports that the extension has been configured by the developer to have this (large) access.
But, on the user side (line just below), you can limit the thing.
I reproduced with uBlock Origin for Peter Lowe list @gwarser.
settings:
mismatched error (network conection is fine):
Extensions background page can access any URL, no matter the permission, when server responds with proper CORS header (basically access-control-allow-origin: *
). in uBO, lists mirrored on github.io
are downloaded without errors, because it uses CORS.
AdGuard's servers work fine.
@gwarser That's a good news! A proper fix for this issue is possible therefore. ✔️
No problem of course when the "Site access" value is set on "On all sites": screenshot
And when set on "On specific sites" (I just put Google's main domain name to test):
screenshot
↬ No problem for GitHub's nor GitLab's domain names (despite not allowed — thanks to proper CORS header present).
↬ Only pgl.yoyo.org
from @pgl has indeed a problem (due to this lack of proper CORS header). :relaxed:
(Despite a 200 OK
—but in red—, you have this problematic response instead of that normal one.)
But, as @gwarser said, AdGuard's servers are fine regarding CORS header stuff (I only added the FRA: AdGuard Français
filter list to the default uBO configuration, to test).
So … AdGuard's servers are OK under uBO but not under AdGuard Browser extension … 🤔
Regarding the latter, see screenshots of: ✖️ frontend error, backend error 1, backend error 2 (and backend errors overview).
…Versus, when set on "On all sites" (only Base filter used here, just for info, but same with various ones that got correctly updated): ✔️ frontend OK, backend OK 1, backend OK 2 (and backend OK overview). ↪️ Instead of a OPTIONS request (receiving a 403 Forbidden): - we see two GET requests (both receiving a 200 OK); - plus the request to the Base filter file (2.txt), only because an update was available in this case. Else, request not present.