Page 1 of 1
How to un-block dynamic content from Google AJAX Feed API
Posted: Fri Sep 25, 2009 4:51 pm
by RZ
After I updated to NoScript 1.9.9.01, content that had previously never been blocked is now blocked (using Firefox 3.0.1.0). This is an example of where it's happening:
http://www.romepubliclibrary.org/ (the center column should have content from an RSS feed that is displayed on the page with a script that uses the Google AJAX Feed API). I can't figure out how to un-block it in the NoScript options. The page works when NoScript is disabled.
This is what I tried:
- Installed NoScript 1.9.9.02 (no change)
- Unsuccessfully tried adding the domain name to the Anti-XSS Protection Exceptions. No idea if this would help or not, but when I try it, anything I type into the Pattern matching sample box turns red and is not added to the list when I click OK. (So right now I can't seem to add anything to the Anti-XSS Protection Exceptions -- not sure if this is related to the original problem or not.)
Any suggestions would be appreciated -- thanks!
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Fri Sep 25, 2009 6:24 pm
by Giorgio Maone
You need all the following 3 to be allowed:
- romepubliclibrary.org
- google.com
- lib.wi.us
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Fri Sep 25, 2009 7:11 pm
by RZ
All three addresses are in my Whitelist already, so I don't think that's the problem. If it should be in another place too, please let me know.
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Fri Sep 25, 2009 7:55 pm
by Giorgio Maone
It's working for me with those.
Could you try using NoScript Options|Reset and reallowing them?
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Fri Sep 25, 2009 10:34 pm
by GµårÐïåñ
It works fine, unless you have RequestPolicy which blocks access to google.com and lib.wi.us but otherwise it should work fine.
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Thu Oct 01, 2009 6:21 pm
by RZ
Giorgio Maone wrote:Could you try using NoScript Options|Reset and reallowing them?
I reset the options, allowed the specific URLs NoScript was blocking, and set it to Allow Scripts Globally, but this still does not fix it.
GµårÐïåñ wrote:It works fine, unless you have RequestPolicy which blocks access to google.com and lib.wi.us but otherwise it should work fine.
I do not have RequestPolicy, but respectfully, it is not working fine for me.
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Thu Oct 01, 2009 6:51 pm
by Giorgio Maone
Have you got AdBlock Plus?
Does disabling NoScript actually fix this issue?
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Thu Oct 01, 2009 7:28 pm
by RZ
I don't have AdBlock, and for the add-ons I do have, disabling all of them (while leaving NoScript enabled) doesn't have an effect.
Disabling NoScript DOES fix the problem, though.
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Thu Oct 01, 2009 8:00 pm
by Giorgio Maone
Can you see any error message in Tools|Error Console when you load the page?
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Thu Oct 01, 2009 8:42 pm
by RZ
Yes-- this is what it says (how do I fix it?):
[ABE] <LOCAL> Deny on {GET
http://www.scls.lib.wi.us/rom/homepage-blog-text.js <<<
http://www.romepubliclibrary.org/,
http://www.romepubliclibrary.org/}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Thu Oct 01, 2009 8:53 pm
by Giorgio Maone
Oh, finally.
This explains why you're the only one here observing this issue: the
http://www.scls.lib.wi.us domain points to a host inside your local network!
Are you an employee of the Wisconsin State?
Anyway, to work-around, you can open
NoScript Options|Advanced|ABE and either disable the SYSTEM ruleset (not recommended) or edit it inserting the following rule in its beginning:
Re: How to un-block dynamic content from Google AJAX Feed API
Posted: Thu Oct 01, 2009 9:23 pm
by RZ
VERY interesting. It's working properly now with the ABE user-ruleset in place. Thank you for your help in troubleshooting this issue.