Reviews for HTTPS Everywhere
HTTPS Everywhere by EFF Technologists
Rated 5 out of 5
2,017 reviews
- by Firefox user 13417750, 8 hours agoRated 5 out of 5
- by palopezv, 9 hours agoRated 4 out of 5
- by saint23thomas, 2 days agoRated 4 out of 5
- by Firefox user 16732967, 2 days agoRated 3 out of 5
- by i.blast, 4 days agoRated 5 out of 5
- by Ax, 4 days agoRated 5 out of 5
- by Firefox user 15025408, 4 days agoRated 5 out of 5
- by Bob Silverberg, 4 days agoRated 5 out of 5
- by Firefox user 16725075, 5 days agoRated 1 out of 5
- by Dark Thoughts, 5 days agoRated 4 out of 5It's a good addon, but is there a point in using it past FF83? To me it seems that it now supports the exact same functionality natively, without the need to use a third party addon like this.
- by Torcerdra, 5 days agoRated 5 out of 5
- by Bellnox, 6 days agoRated 5 out of 5
- by Firefox user 15197218, 7 days agoRated 5 out of 5
- by harley, 7 days agoRated 5 out of 5
- by Sergey Ivanov, 7 days agoRated 3 out of 5It has been great until recently, when I started experiencing severe lagging in Firefox and discovered that this extension is a memory hog.
Here's my `top` with HTTPS Everywhere enabled:
PID PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9036 20 0 14.6g 218564 107332 S 0.0 1.3 0:25.73 WebExtensions
...and when the add-on is disabled:
PID PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9036 20 0 8970992 199000 107204 S 0.3 1.2 0:26.00 WebExtensions
I have no idea why it needs to commit 14Gb of virtual memory, but that does not sound reasonable at all. I'll keep it switched off for now to see if the overall performance improves.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
$ uname -a
Linux xxxxx 5.4.0-66-generic #74-Ubuntu SMP Wed Jan 27 22:54:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ firefox --version
Mozilla Firefox 86.0
HTTPS Everywhere Version 2021.1.27 - by Firefox user 15316639, 9 days agoRated 5 out of 5
- by S200, 9 days agoRated 1 out of 5Hola,
El complemento es funcional respecto a los sitios Web donde no haya implementado https (seguro).
En algunos sitios Web´s el acceso es bloqueado por el complemento HTTPS everywhere.
www.orangepi.org (microordenadores)
En otros sitios Web´s el acceso esta desbloqueado por el complemento HTTPS everywhere.
www.raspberrypi.org (microordenadores)
Enlaces rotos del "foro" en orangepi.org no este actualizados o esten dirigidos a otros dominios que no tienen implementado https por defecto teniendo que bloquear el acceso completo al sitio Web, entonces ¿como creo una regla para incluirlo en la lista permitidos?
Deshabilitando la funcion HTTPS del complemento y activar HTTPS desde el navegador para acceder al sitio Web ocurre lo mismo.
Aunque menos quebraderos desactivando el modo solo HTTPS everywhere y HTTPS navegador para un sitio en particular. - by Rico Liebscher, 9 days agoRated 5 out of 5
- by cyklope, 10 days agoRated 4 out of 5
- by LarryRay Mullinski, 10 days agoRated 5 out of 5
- by AliYarjanli, 10 days agoRated 5 out of 5
- by Anzani, 11 days agoRated 5 out of 5
- by zhooe, 13 days agoRated 5 out of 5
- by Firefox user 16081223, 13 days agoRated 5 out of 5