We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

Toto vlákno bylo archivováno. Pokud potřebujete pomoci, založte prosím nový dotaz.

lost protocol in url

  • 1 odpověď
  • 1 má tento problém
  • 10 zobrazení
  • Poslední odpověď od cor-el

goodguy00
goodguy00
more options

when working on local sites (ie sites with no domain, like http://myserver/dir1/file.html), FF tends to forget the protocol in the url field (simply omits the "http://"). this is no big deal, unless you click into it and eg. change some filename and send that. then, logically, FF thinks it's a search-string and redirects you to the primary search engine (eg. google) with your local url as the search criteria, which is plain wrong.

when working on local sites (ie sites with no domain, like http://myserver/dir1/file.html), FF tends to forget the protocol in the url field (simply omits the "http://"). this is no big deal, unless you click into it and eg. change some filename and send that. then, logically, FF thinks it's a search-string and redirects you to the primary search engine (eg. google) with your local url as the search criteria, which is plain wrong.

Všechny odpovědi (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Try to set browser.urlbar.trimURLs = false on the about:config page.

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.