Closed Bug 617881 Opened 15 years ago Closed 7 years ago

Stupid awesomebar selection (https vs http)

Categories

(Firefox :: Address Bar, defect)

Product:
Firefox
Component:
Address Bar
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INACTIVE

People

(Reporter: djc, Unassigned)

Details

I regularly surf to a web application that's available over both http and https. I used to use the http version, but have since tried to use the SSL version every time. However, it appears some of my attempts are thwarted by the way the Awesomebar frecency suggestions work. Here's some concrete behavior that seems preventable: 1. Type 'https://sftp' 2. First suggestion is 'http://sftp.example.com/' - Desired suggestion (second) is 'https://sftp.example.com/' It seems like it should be possible to make the correct guess here. (As a somewhat separate issue, perhaps the location bar should always select the SSL variant if both are available.)
(This is with 4b7, BTW.)
common protocols (http://, https://) are removed from the search string, by design. thus your 'http://sftp' is equal to searching 'stftp'. The point is that you have to write less and we give you more results to choice from. I'd guess you could type something like 'https sftp' to get what you want.
If I do type one of the common protocols, would it be very hard to honor it? Seems like that would make the searching more predictable and therefore usable.
it would make more predictable for you, but most less advanced users type the protocol just because they think they have to, and this causes both fewer results and slower searches.
Note that you can remove the entry that you don't want to use anymore by selecting it in the location bar, and pressing shift+delete.
What about always giving a https url a higher priority than the equivalent http URL?
(In reply to Adrian from comment #6) > What about always giving a https url a higher priority than the equivalent > http URL? it may be feasible giving a bonus to secure pages, it may have unexpected effects though.
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.