Closed
Bug 723622
Opened 13 years ago
Closed 7 years ago
Awesomebar should not ignore typed protocols
Categories
(Firefox :: Address Bar, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: sec-want, Whiteboard: [sg:want P5])
If I start by typing "https:", only https URLs should be autocompleted.
It makes sense to ignore the protocol when the protocol was added by selecting an autocomplete entry (which was the scenario in bug 424717), but when the protocol was typed by the user, it shouldn't be ignored.
Comment 1•11 years ago
|
||
And conversely, if I type an address with an explicit "http://" beginning, then I want and expect to be sent to the non-SSL page.
As of 32.0.3 if you have ever visited the SSL-version of a page, FF redirects you there even if you request http. This prevents users from logging into captive portals: instead of the portal login screen, they are greeted with about:certerror. The certificate warning is misleading and, worse, the 'add exception' button is not shown which means the only workarounds are to either history->'forget this site' or navigate to a page never visited before (via http).
There is work being done on captive portal detection (bug 562917) but meanwhile, making the location bar respect the user-specified protocol would provide a simpler and more obvious workaround.
Comment 2•11 years ago
|
||
(In reply to Patrick O'Keeffe from comment #1)
> And conversely, if I type an address with an explicit "http://" beginning,
> then I want and expect to be sent to the non-SSL page.
that's what the awesomebar is doing. if you type the protocol, it's respected, if you don't type it, we guess based on what you typed before.
Comment 3•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•