Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Тази тема беше затворена и архивирана. Моля, задайте нов въпрос ако имате нужда от помощ.

Firefox built in HTTPS vs HTTPS Everywhere extension?

  • 4 отговора
  • 1 има този проблем
  • 4476 изгледи
  • Последен отговор от ARMAN KHAN

more options

What's the difference between firefox https and everywhere https extension? are they the same? see attached screenshots

What's the difference between firefox https and everywhere https extension? are they the same? see attached screenshots

Избрано решение

Hello,

Although HTTPS Everywhere is good, in many ways it is worse than Firefox's built in protection.

All extensions get a process, so having the function as a normal feature cuts down on processes and resource usage (although minimally, it does affect a tiny bit)

The inbulilt HTTPS protection also respects themes, allowing for a more seamless experience.

All in all, HTTPS Everywhere served its purpose for a time, but is now unneeded, as the inbuilt one is simply better.

Прочетете този отговор в контекста 👍 1

Всички отговори (5)

more options

Избрано решение

Hello,

Although HTTPS Everywhere is good, in many ways it is worse than Firefox's built in protection.

All extensions get a process, so having the function as a normal feature cuts down on processes and resource usage (although minimally, it does affect a tiny bit)

The inbulilt HTTPS protection also respects themes, allowing for a more seamless experience.

All in all, HTTPS Everywhere served its purpose for a time, but is now unneeded, as the inbuilt one is simply better.

more options

andmagdo said

Hello, Although HTTPS Everywhere is good, in many ways it is worse than Firefox's built in protection. All extensions get a process, so having the function as a normal feature cuts down on processes and resource usage (although minimally, it does affect a tiny bit) The inbulilt HTTPS protection also respects themes, allowing for a more seamless experience. All in all, HTTPS Everywhere served its purpose for a time, but is now unneeded, as the inbuilt one is simply better.

Thanks for clarifying, i will stick with the built in HTTPS.

more options

hii

Firefox_Bug_Report,

HTTPS Everywhere is a free and open-source browser extension for Google Chrome, Microsoft Edge, Mozilla Firefox, Opera, Brave, Vivaldi and Firefox for Android, which is developed collaboratively by The Tor Project and the Electronic Frontier Foundation (EFF).[4] It automatically makes websites use a more secure HTTPS connection instead of HTTP, if they support it.[5] The option "Encrypt All Sites Eligible" makes it possible to block and unblock all non-HTTPS browser connections with one click.[6] Due to the widespread adoption of HTTPS on the internet, and the integration of HTTPS-only mode on major browsers, the extension will be retired at the end of 2022.[7] Thanks regards -Arman

more options

This question has been locked because the original author has deleted their account. While you can no longer post new replies, the existing content remains available for reference.