ABE blocking page, unable to debug the cause
Posted: Mon Nov 10, 2014 3:05 pm
Hello,
I'm here to ask how to debug abe properly and what could be the cause of a blocked site:
I'm unsing noscript 2.6.9.3 and visiting www.autistici.org , www.inventati.org , all on the same server and resolving to
www.autistici.org is an alias for www.l.autistici.org.
www.l.autistici.org has address 82.94.249.234
www.l.autistici.org has IPv6 address 2001:888
56::19
www.l.autistici.org has IPv6 address 2002:b2ff:9023::1
www.l.autistici.org has IPv6 address 2a01:4f8:141:2f0::19
I see abe blocking that request with this error:
[ABE] <LOCAL> Deny on {GET https://www.autistici.org/en/index.html <<<
https://www.autistici.org/, chrome://browser/content/browser.xul - 6}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny
I cannot see the real request that is triggering one of those rules, so not being able to debug that properly.
The error was not there probably some noscript version ago, but for now I'm not able to check with previous versions.
Also note that those resolved ip could be different based on your location because of dns geolocation redirects but I have reports of other people from various parts of the world having the same issue.
any help really appreciated.
bye
--s.
I'm here to ask how to debug abe properly and what could be the cause of a blocked site:
I'm unsing noscript 2.6.9.3 and visiting www.autistici.org , www.inventati.org , all on the same server and resolving to
www.autistici.org is an alias for www.l.autistici.org.
www.l.autistici.org has address 82.94.249.234
www.l.autistici.org has IPv6 address 2001:888
www.l.autistici.org has IPv6 address 2002:b2ff:9023::1
www.l.autistici.org has IPv6 address 2a01:4f8:141:2f0::19
I see abe blocking that request with this error:
[ABE] <LOCAL> Deny on {GET https://www.autistici.org/en/index.html <<<
https://www.autistici.org/, chrome://browser/content/browser.xul - 6}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny
I cannot see the real request that is triggering one of those rules, so not being able to debug that properly.
The error was not there probably some noscript version ago, but for now I'm not able to check with previous versions.
Also note that those resolved ip could be different based on your location because of dns geolocation redirects but I have reports of other people from various parts of the world having the same issue.
any help really appreciated.
bye
--s.