搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Is it possible to allow exceptions for automatically adding https:// to websites

  • 5 个回答
  • 3 人有此问题
  • 4 次查看
  • 最后回复者为 MozillaBurger

more options

I was wondering if it was possible to allow firefox to add a http:// on specific websites rather than the usual https://. This would mainly be for websites that do not support SSL. An example would be reddit where typing reddit.com into the address bar redirects me to https://www.reddit.com which is an invalid site. Is it possible to add it as an exception?

I was wondering if it was possible to allow firefox to add a http:// on specific websites rather than the usual https://. This would mainly be for websites that do not support SSL. An example would be reddit where typing reddit.com into the address bar redirects me to https://www.reddit.com which is an invalid site. Is it possible to add it as an exception?

被采纳的解决方案

Could it be that autocomplete gets you the https prefix / prefixes from the history? Check the history contents for "https" entries.

定位到答案原位置 👍 1

所有回复 (5)

more options

Firefox doesn't force HTTPS - do you have an add-on installed which is causing that?

Like maybe HTTPS Anywhere?


http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes

more options

The strange thing is that I do not have any such plug in. I have also noticed that FF tends to autocomplete single words in the address box even though I tweaked it in about:config to just carry out a google search.

more options

选择的解决方案

Could it be that autocomplete gets you the https prefix / prefixes from the history? Check the history contents for "https" entries.

more options

Cleared it and it seems to have settled. Thanks

more options

That isn't a solution. The next time he goes to an HTTPS version of that site, FF *will* in fact force it every time he goes back there. Without any plugins or extensions. This issue has been raised over and over, and it is an issue with the auto complete. But nobody at FF seems to want to fix it.

https://support.mozilla.org/en-US/questions/933470