Web Applications Stack Exchange is a question and answer site for power users of web applications. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Facebook gives you the option to always use https, which obviously is a lot safer, but why do they give people the option? Why don't they just force everyone to use it? Is there ay reason why you wouldn't want https on? It looks like https doesn't impact performance too much.

share|improve this question
Only Facebook can answer this. All else is speculation. – Al E. Mar 4 '13 at 16:20
up vote 1 down vote accepted

Https is more processor intensive and slower as it is harder to cache etc because everything that is sent is encrypted so you can't share with others. Also encrypted data tends to take up more KB. Its a particular problem if you are encrypting images.

People who are still using slow connections may wish to avoid https use.

share|improve this answer

Per https://www.facebook.com/notes/facebook-engineering/secure-browsing-by-default/10151590414803920

Some mobile phones and mobile carrier gateways don't fully support https. While we're working with the vendors of these products, we didn't want to leave https off entirely for affected users. Instead, we only downgrade the session on an ineligible device while continuing to use

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.