[HTTPS-Everywhere] facebook rule

[Nitrox]

On 25 October 2010 23:01, Cesare <voltsz at gmail.com> wrote:

> Anybody use the HTTPS FB site and have no problem to use chat and/or
> use the photo without problem?
>
> If I use the HTTPS version of FB, I encountered probkem to use chat
> and photo (also the site is very slow).
>
> Cesare
>
>
The questions you asked were already answered in the FAQ.
https://www.eff.org/https-everywhere/faq/

 *Q. Why does Facebook chat not work with HTTPS Everywhere?*
>
> A. The HTTPS version of facebook.com appears not to support chat. There's
> not much we can do about that unless and until Facebook adds an HTTPS
> version of chat. If you'd like to use HTTPS Everywhere for other sites, but
> want to keep using the unencrypted version of Facebook so that you can chat,
> you can do that by going into the Tools->Add Ons->HTTPS
> Everywhere->Preferences dialog and unchecking the Facebook rule.
>  *Q. Isn't it more expensive or slower for a site to support HTTPS
> compared to regular HTTP?*
>
> A. It can be, but some sites have been pleasantly surprised to see how
> practical it can be. Also, experts at Google are currently implementing
> several enhancements to the TLS protocol that make HTTPS dramatically
> faster; if these enhancements are added to the standard soon, the speed gap
> between the two should almost disappear. See Adam Langley's description of
> the HTTPS deployment situation<http://www.imperialviolet.org/2010/06/25/overclocking-ssl.html>for more details on these issues. Notably, Langley states: "In order to
> [enable HTTPS by default for Gmail] we had to deploy no additional machines
> and no special hardware. On our production frontend machines, SSL/TLS
> accounts for less than 1% of the CPU load, less than 10KB of memory per
> connection and less than 2% of network overhead."
>
> Although we're quite concerned about the certificate authority system,
> certificates in the current system are now quite cheap — paid certificates
> can cost just ten to twenty dollars a year.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.eff.org/pipermail/https-everywhere/attachments/20101026/3933fc57/attachment.html>