InformAction Forums

Giorgio Maone wrote:OK, I managed to make it work after adding 127.0.0.1 (no protocol, no port) to my whitelist.
Of course, the ABE rule exception is still needed. Updated the FAQ entry to reflect this finding.

That did the trick. Thanks.

Thank you so much -- that did it, finally!

For me, allowing http://127.0.0.1:0 got me to the Select Photo popup, but then it froze before displaying the file tree -- even cancelling the popup was impossible. The NoScript menu presented the option to allow http://127.0.0.1:54273, and doing so restored full functionality. Not sure if that port is the only one serving that page -- it would be a real pain to have to add port after port. Unlike the ABE editor, the Whitelist apparently does not permit the * wildcard, and ":0" did not function as you would want a wildcard to function, since it still was necessary to add the specific port.

Malbone wrote:The Whitelist apparently does not permit the * wildcard, and ":0" did not function as you would want a wildcard to function, since it still was necessary to add the specific port.

For historical and technical reasons, port wildcard in NoScript whitelist is "0" rather than "*".
In the upcoming stable release(1.9.9.60), "127.0.0.1" will be shown in the menu and everything should work just fine as soon as you allow it (you still need the ABE rule, though).

[EDITED, latest dev build still doesn't show the raw IP for non-standard port URLs, it's a 1.9.9.60 enhancement.]

I added the rule to ABE system rules, and 127.0.0.1 to Whitelist, yet the Facebook photo uploader is still blocked unless I turn off ABE. Am I doing something wrong?

# Facebook Photo Uploader Plugin exception
Site http://127.0.0.1:*/photos/uploader_iframe.php?*
Accept from *.facebook.com

@Moon Juice:
is that rule the very first of the ruleset?
If it is (as it should), could you show me the exact [ABE] line you get in Tools|Error Console when this happens?

Giorgio Maone wrote:@Moon Juice:
is that rule the very first of the ruleset?
If it is (as it should), could you show me the exact [ABE] line you get in Tools|Error Console when this happens?

It is not the first listed under ABE "system" rules, but the 2nd. Is this wrong?

No "error" in error console, just a ton of warnings and the following Message:

[ABE] <LOCAL> Deny on {GET http://127.0.0.1:3114/photos/uploader_i ... aid=165034 <<< http://www.facebook.com/, http://www.facebook.com/ - 7}
SYSTEM rule:
Site LOCAL
Accept from LOCAL
Deny

Moon Juice wrote:

Giorgio Maone wrote:@Moon Juice:
is that rule the very first of the ruleset?
If it is (as it should), could you show me the exact [ABE] line you get in Tools|Error Console when this happens?

It is not the first listed under ABE "system" rules, but the 2nd. Is this wrong?

Yes it is. Rules in a ruleset are processed from top to bottom, and the first match wins (in this case, the Deny from the LOCAL rule).

It *seems* to be working now that I have sorted the order. Thanks! I'll post back if I run into further trouble.