Should the AwesomeBar drop down filter out URLs that are immediately redirected from domain.com to www.domain.com?

RESOLVED INACTIVE

Status

()

Firefox
Address Bar
--
enhancement
RESOLVED INACTIVE
7 years ago
a month ago

People

(Reporter: Cngevpxhaqrefpber, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

I was thinking that it might be nice if the AwesomeBar dropdown filtered out URLs in the history that are immediately redirected from domain.com to www.domain.com.

For example, when I go to Google, I type "google.com". I am then redirected to "www.google.com" by Google. However, when I type "google" in the AwesomeBar later, there are two items at the top of the dropdown: one for www.google.com (which shows the Google favicon next to it) and the next one below it for google.com (which doesn't show the Google favicon next to it, and doesn't contain the www in the URL).

Not sure if this is even possible or would cause any issues, but I think it would make the drop down list cleaner if those domain.com URLs that are simply immediately redirected to www.domain.com could be hidden from the AwesomeBar drop down.

Reproducible: Always

Steps to Reproduce:
1. Go to a website that redirects you to www.domain.com, such as mozilla.org, google.com, etc.
2. Close the tab, open a new one, and start typing the URL again (such as "goog").
3. Note there are at least two drop down items for the URL you visited: one being www.google.com, another below it being google.com.

Comment 1

7 years ago
Duplicate candidates:
Bug 426142 - Awesomebar does not learn from HTTP 301 Moved Permanently responses
Bug 576405 - Location bar should be aware of HTTP 301s
Bug 434947 - redirect urls appear in location bar autocomplete
OS: Windows 7 → All
Hardware: x86 → All
Version: unspecified → Trunk

Comment 2

a month 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: UNCONFIRMED → RESOLVED
Last Resolved: a month ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.