Page 1 of 1

[INVALID] Facebook privacy conf. don't work with HTTPS

Posted: Wed Jul 14, 2010 9:46 pm
by andyvec
This is a bug I found a few months ago but still continued with problems. I use Ubuntu with the lastest version of Firefox and NoScript, but i also have a netbook with Windows 7 and is the same problem.

I use NoScript to enforce HTTPS protocol to encrypt the data in Facebook, I added "*.facebook.com" in the NoScript HTTPS configuration and I can use Facebook with HTTPS but I can't enter to the "Privacy configuration" if I have NoScript on (Desactivating NoScript everything works fine)

Firefox show this warning (I translated from spanish to english):
The site is not being redirected correctly

Firefox has detected that the server is redirecting the request to https://http://www.facebook.com/setting ... acy&ref=mb in a way that will never complete.

This problem is sometimes caused by disabling or decline cookies.
I hope this will help you to solve the problem

Re: Facebook privacy configuration don't work with HTTPS

Posted: Sat Aug 28, 2010 2:31 am
by rickmastfan67
I'll second this. This is really annoying. Only can get into "My Account | Settings" with HTTPS forced on Facebook. If I want to go into any of my other settings (like Networks, Notifications), I have to disable the forced HTTPS on Facebook to do so. :|
Also, I can't even get into the "Privacy Settings" with HTTPS forced on. :cry:

Windows 7 x64
FF 3.6.8 (32bit)
NS 2.0.2.3

Re: Facebook privacy configuration don't work with HTTPS

Posted: Sat Aug 28, 2010 11:52 am
by Giorgio Maone
I hope you understand this is not a NoScript bug, but a Facebook problem: they don't have the correct certificate setup for all the "important" domains of theirs, and they're forcing some parts of their site to HTTP. So when NoScript forces HTTPS they redirect to HTTP, then NoScript forces again to HTTPS and so on ad infinitum.

There's nothing you (or NoScript) can do to make those page work in HTTPS: you can either give up using them entirely, or use them in HTTP.
To do so you may want to set one or more exception patterns in NoScript Options|Advanced|HTTPS|Behavior|Never force HTTPS on the following sites.