Whitelisting content from 192.168.*

General information, announcements and questions about the EasyList subscriptions.
Locked
guest
Guest

Whitelisting content from 192.168.*

Post by guest »

Code: Select all

@@||192.168.$xmlhttprequest
@@||192.168.*/images/adv_
Could these whitelists, especially the xmlhttprequest one, please be removed? They're interfering with my usage of a local server in that IP address range to test my adblock, and I don't think I can change the IP address to a different range. Thanks
User avatar
fanboy
EasyList Author
EasyList Author
Posts: 12223
Joined: Wed Sep 05, 2007 8:17 pm

Post by fanboy »

Most likely added because of routers being problematic with adblock plus, just easier to just disable those filters?
guest
Guest

Post by guest »

Thanks for the reply
That works in Gecko-based browsers, but it's a bit of a pain doing that repeatedly on a disk-protected VM, and ABP in Chromium doesn't appear to have that feature.

The /images/adv_ rule, I could try to remember it's there and make sure to rewrite any relevant URLs on the server to not be named like that (unless I want them unblocked), but there's no way to avoid using XHR in this case.
barbaz
Postaholic
Postaholic
Posts: 204
Joined: Mon Sep 15, 2014 12:55 am

Post by barbaz »

Bump
(I was the guest)

Code: Select all

@@||192.168.$xmlhttprequest
is still in the filter subscription. Any updates on removing it, or am I stuck using my local test site with only Gecko based browsers and disabling that filter as needed?
User avatar
smed79
Liste AR/FR Author
Liste AR/FR Author
Posts: 15839
Joined: Sun Jan 17, 2010 4:00 am
Location: EasyList Forum

Post by smed79 »

•► Read RULES / Use forum Search
••► Don't post clickable links
•••►Upload screenshots at imgbb.com
barbaz
Postaholic
Postaholic
Posts: 204
Joined: Mon Sep 15, 2014 12:55 am

Post by barbaz »

Thanks but unfortunately ~third-party doesn't help here, as all XHR with my server have to be 1st-party.

(noting here as well, https://hg.adblockplus.org/easylist/rev/2178f5f41c25)
My server is not at 192.168.1.1. If that one rule could be limited to affect only at 192.168.1.1, that would be awesome.
User avatar
fanboy
EasyList Author
EasyList Author
Posts: 12223
Joined: Wed Sep 05, 2007 8:17 pm

Post by fanboy »

The rule seems fine, it covers 192.168.* which includes 192.168.1.1, 192.168.0.1
barbaz
Postaholic
Postaholic
Posts: 204
Joined: Mon Sep 15, 2014 12:55 am

Post by barbaz »

My server isn't at 192.168.0.1 either... I guess what you're saying is that people will have their routers at different IPs in that range so it can't be reasonably limited to specific IP(s) in a subscription that's so widely used.

Last question: assuming my router is at 192.168.0.1 and its interface needs the exception for XHR, which of these modifications to that whitelist filter would best preserve the filter's original intent?

Code: Select all

@@||192.168.$~third-party,xmlhttprequest,domain=192.168.0.1

Code: Select all

@@||192.168.0.1^$~third-party,xmlhttprequest
User avatar
fanboy
EasyList Author
EasyList Author
Posts: 12223
Joined: Wed Sep 05, 2007 8:17 pm

Post by fanboy »

domain=192.168.0.1 becomes redundant since is already whitelisting http://192.168.*.*

If you have a issue report link of the issue I'll gladly look at it.
barbaz
Postaholic
Postaholic
Posts: 204
Joined: Mon Sep 15, 2014 12:55 am

Post by barbaz »

fanboy wrote:If you have a issue report link of the issue I'll gladly look at it.
Thanks, issue report will be sent by PM.
barbaz
Postaholic
Postaholic
Posts: 204
Joined: Mon Sep 15, 2014 12:55 am

Post by barbaz »

... and this topic was concluded by PM. Bottom line is, my configuration is too unusual to be worth writing exception for.
Since I've got a server anyway, what I will have to do is drop a custom variant of EasyList on that server (removing or altering the problematic whitelist) and use that with my adblock test.
Locked