Facebook problem

[cocoapuff]

Probably this question is already answered somewhere but I did not find it via forum search or looking at the FAQ. I cannot get to a Facebook page, there appears to be some sort of infinite loop going on, only the top part of the page loads and the rest never completes.


Relevant extensions:

NoScript 2.1.0.1

HTTPS Everywhere 0.9.9.development.4


Relevant settings in NoScript:

USER
Site .facebook.com .fbcdn.net
Accept from .facebook.com .fbcdn.net
Deny INCLUSION(SCRIPT, OBJ, SUBDOC)


Relevant settings in HTTPS Everywhere:

Facebook ON
Facebook+ ON


Messages in error console include:

http://www.facebook.com : server does not support RFC 5746, see CVE-2009-3555

[NoScript HTTPS] AUTOMATIC SECURE on https://www.facebook.com: reg_fb_ref=https%3A%2F%2Fwww.facebook.com%2Fpeople%2F[NAMEREDACTED]2F[9-digit numerical string]D; domain=.facebook.com; path=/; Secure

Lots of "Unknown property, declaration ignored" warnings

Finally, [NoScript] Blocking refresh on unfocused tab, https://www.facebook.com/people/[NAMEREDACTED]/[9-digit numerical string]?_fb_noscript=1->https://www.facebook.com/people/[NAMEREDACTED]/[9-digit numerical string]?_fb_noscript=1 (guess that was when I hit the "X" to stop the page from attempting to load)

Many apologies if I'm missing something very simple...

[GµårÐïåñ]

To the best of my knowledge, Facebook does NOT support SSL (aka HTTPS) and that's why you might be facing this issue. When you force it using NoScript and it doesn't support it or any other addon, the content will tend to not load since they are deemed not qualifying. I could be wrong, so I will defer to Giorgio but in short I believe that's your issue.

EDIT: Although you can force the main Facebook page and services to use HTTPS, with allowing akamaihd.net for all the pictures and stuff of your friends, anything running as an app on the service will not load unless they support it on their OWN container side as well. Otherwise you get this message:

Switch to regular connection (http)?
Sorry! We can't display this content while you're viewing Facebook over a secure connection (https).
Would you like to temporarily switch to a regular connection (http) to use this app?
You will have a secure connection upon your next login.

NOTE: Apps are hosted on the provider's third-party servers and loaded within a facebook IFRAME container and so your rule in ABE will break them (fail to load), your HTTPS enforcement (if they don't support it on their own side) will make it not load, so there is alot that can go wrong when its not enforced by Facebook across ALL ranges. Hope that helps.

[cocoapuff]

Hello, thank you for taking the time to write that.

I do not get the message you quoted from Facebook, by the way. In HTTPS Everywhere, I turned off the two rules for Facebook and Facebook+ [Apps], restarted Firefox, the page still won't load. It just cycles very rapidly between facebook.com and static.ak.fbcdn.net but the page load never completes.

Next, I would like to exclude NoScript as a source of the problem, can you tell me how to do that? I guess simplest would be to deactivate the extension.

[GµårÐïåñ]

Hello, thank you for taking the time to write that.

I do not get the message you quoted from Facebook, by the way. In HTTPS Everywhere, I turned off the two rules for Facebook and Facebook+ [Apps], restarted Firefox, the page still won't load. It just cycles very rapidly between facebook.com and static.ak.fbcdn.net but the page load never completes.

Next, I would like to exclude NoScript as a source of the problem, can you tell me how to do that? I guess simplest would be to deactivate the extension.

Best way to eliminate NoScript in all cases is to either disable all addons in that profile EXCEPT NoScript and restart and try to see if it works. Or create a blank profile with NoScript only installed and test it that way. In the clean profile you eliminate any other stuff that can interfere so you get a truer picture of NS involvement but if you want to make a quick test, disabling everything but NS works too but could be affected by any changes made by other addons that will still be in play even if they are disabled. Good luck and let us know if you find anything.