Misreprented URL; potential misdirect problem....




11 years ago
11 years ago


(Reporter: educmale, Unassigned)


Firefox Tracking Flags

(Not tracked)




11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20071115 Firefox/
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20071115 Firefox/

This listed URL purports to be a google search:


A hover on this URL shows off this precise URL in the status area

However, clicking on this URL returns the following web page:


and not a google search.  

The misdirection, as with all misdirections, I thought was not supposed to happen any more.  I am assuming, mostly, that this is a artifact of a defect in Google, and not the failure of FireFox, though I wonder why this is not detected.  

I also recognize that this report may be in the wrong section; and won't be hurt if someone puts it in the right place.

Reproducible: Always

Steps to Reproduce:
The "btnI=" part in the URL means the same thing as if you used the "I'm Feeling Lucky" button when searching. "I'm Feeling Lucky" means you're instantly redirected by Google to the first hit for the query (in this case, |inurl:cialize welcome|). Check out http://www.google.com/search?hl=en&q=inurl:cialize+welcome to see the real Google search results. Note that the only query is that website, so that's why you're being redirected there.
Last Resolved: 11 years ago
Resolution: --- → INVALID

Comment 2

11 years ago
Ah.  Interesting.  My thanks for pointing that out.

Then my vote is to make this 'resolved invalid' bug into something that advocates for a FireFox modification that catches that particular google redirect, and advising the user.  Now that I know how this works, I can see how it would be available for abuse.  I'm not sure if I am 'authorized' to reopen the bug, Reed, or just make the suggestion.

Again, not sure if this is the place to put that bug or modification request forward, and would not be offended if it is properly directed.
You need to log in before you can comment on or make changes to this bug.