So, keep in mind that if you visit a page that isn’t on secure (https) that you double check your settings and re-enable the secure connection settings again. Now you’re back to a secure (https) connection. Then check the box next to Browse Facebook on a secure connection (https) whenever possible again to re-enable the setting…make sure to click the Save button.Ĩ. If your Opengear appliance is running firmware 3.16.4 or Lighthouse 4.5. Under Account Security click on Change.ħ. Newer versions of Chrome, Firefox, Internet Explorer and other browser will no longer connect to servers enabled with insecure ciphers.
Once that is completed, click the Custom button from the Trusted Sites zone and locate the option for Display mixed. Then click the Sites button and add the Sugar URL to the zone. In IE, go to Tools > Internet Options > Security > Trusted Sites. So what you’ll need to do is go back into your Account Settings.Ħ. Internet Explorer provides your users with the ability to add your Sugar site as a trusted site. And the message advising you need to switch to a regular (http) connection doesn’t say you’ll lose your secure connection after visiting a non-secure site…very annoying.ĥ. If you log out of your account, and sign back in, you’ll notice you’re no longer protected by a secure (https) connection! What? You though you checked a box saying use HTTPS Whenever possible. All browsers will experience this issue (Microsoft Internet Explorer, Mozilla Firefox, Google Chrome). Like in this example where we want to connect to NetworkedBlogs.Ĥ. For instance, if a dashboard page that is located on a secure (https) server contains a viewlet to content on another server that is accessed over an insecure connection (http), that viewlet may be blocked by the browser. At least Facebook gives you a warning…if you want to visit the page, click Continue.ģ.
If you browse to an app or page that is unsecure, you’ll see the following message. When you visit a page or app on Facebook that requires a regular (http) connection, it switches your entire account connection back to the unsecure (http). Unfortunately there’s a flaw in the system. When you check the box Browse Facebook on a secure connection (https) whenever possible you think your always protected right? Not necessarily.Ģ. So you set up secure Browsing (Https) in Facebook to help protect against bad guys running packet sniffing apps like Firesheep over a public Wi-Fi network.
We’ll leave this online for the sake of historical archive and it should be treated accordingly.ġ. Please note: This guide was initially published back in 2011 and Facebook has since resolved this issue and made all of use https, without the need for you to make any changes to your Facebook or browser settings.