ABE blocks local facebook app development

Ask for help about NoScript, no registration needed to post
seaders

ABE blocks local facebook app development

Post by seaders »

Hey guys,

I'm a facebook developer and one of the most common things that you do for developing locally is host map a dummy domain name "mydomain.localhost.com", or similar, to 127.0.0.1 and put that in as your Canvas URL. This allows you to run a server on your local machine, but develop with the full facebook api that you get within a canvas iFrame. The problem, though, is that ABE in NoScript completely blocks this and unless you explicitly put in '127.0.0.1' or 'localhost', you don't even get a notification that it's being blocked. That's a biggie for me, because I lost quite a bit of time thinking that it was my server, my app settings, my problem, my problem because as I said, I got *no notification* about it happening, in Firebug, I'd just see the call to my local server hanging, nothing more.

Anyway, after finding out what was the cause, I definitely like what ABE is doing, and would like to share the solution. In the ABE SYSTEM ruleset, it should already have

Code: Select all

Site LOCAL
Accept from LOCAL
Deny
You've just got to append your app url to that "Accept from" line,

Code: Select all

Site LOCAL
Accept from LOCAL apps.facebook.com/<appname>/
Deny
That's the solution, but not notifying you when those requests are being blocked *really* needs to be fixed.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
dhouwn
Bug Buster
Posts: 968
Joined: Thu Mar 19, 2009 12:51 pm

Re: ABE blocks local facebook app development

Post by dhouwn »

seaders wrote:That's the solution, but not notifying you when those requests are being blocked *really* needs to be fixed.
http://noscript.net/changelog#1.9.5.5 wrote:
  • External requests on default ports to domain names different than "localhost" resolving to 127.0.0.1 don't generate notifications, in order to reduce spam from misconfigured hosts files (activity gets still logged to the Error Console and notifications can be restored by toggling the noscript.ABE.notify.namedLoopback preference)
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Post Reply