Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

FIrefox is always forcing a secure connection to every website I try to visit

  • 2 odpowiedzi
  • 1 osoba ma ten problem
  • 12 wyświetleń
  • Ostatnia odpowiedź od mangoman667

more options

Whenever I type in a URL, I don't usually bother to add http://www. in the URL. This has always worked for me up until a couple of weeks ago. Now, when I don't include this, the URL automatically switches to "https://www." format. For example, when I type "example.com" in the URL bar, it automatically makes the URL "https://www.example.com/". I do not have any add-ons or extensions installed that should cause this problem.

Whenever I type in a URL, I don't usually bother to add http://www. in the URL. This has always worked for me up until a couple of weeks ago. Now, when I don't include this, the URL automatically switches to "https://www." format. For example, when I type "example.com" in the URL bar, it automatically makes the URL "https://www.example.com/". I do not have any add-ons or extensions installed that should cause this problem.

Wybrane rozwiązanie

Does it help if you set the Boolean pref browser.urlbar.autoFill to false on the about:config page?

See "Prevent Firefox from automatically completing URLs":

Przeczytaj tę odpowiedź w całym kontekście 👍 0

Wszystkie odpowiedzi (2)

more options

Wybrane rozwiązanie

Does it help if you set the Boolean pref browser.urlbar.autoFill to false on the about:config page?

See "Prevent Firefox from automatically completing URLs":

more options

Wow, I can actually connect to webpages quickly without getting a 404 error! :) Your first suggestion worked perfectly to resolve my problem. Many thanks! :))