Closed Bug 269600 Opened 21 years ago Closed 21 years ago

get rid of the unnecessary '&client=firefox....' for google search plugin

Categories

(Firefox :: Search, defect)

1.0 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jshin1987, Assigned: bugs)

Details

(Keywords: intl)

This is the other side of a coin to bug 269469. Using 'User-Agent' sent via HTTP, google has no problem recognizing Mozilla Firefox and other gecko-based browser supporting UTF-8. However, in firefox 1.0, google search plugin adds a completely unnecessary (afaict) 'client=firefox....' at the end of the search URL sent to google, which gets in the way of google's ability to recognize firefox as being able to handle UTF-8. If 'client=firefox....' is really necessary, this bug should be invalid and we have to work with google to fix their problem. If it's not, let's just drop '&client=firefox....'. See bug 269469 comment #0 as to how to reproduce (note that it's in UTF-8)
http://bonsai.mozilla.org/cvslog.cgi?file=mozilla/browser/base/content/searchconfig.properties It was added in the above file and there must be a good reason for this. Assuming there is, we have to work with google to make this not get in the way (bug 269469). Before resolving this as invalid, I'm adding a few to Cc to hear what they think.
-> Ben. AFAIK, this will probably be a WONTFIX, but I'll let him make that call.
Assignee: p_ch → bugs
I prefer to ask google to fix their problem (bug 269469), too because that way, it's an instant fix. They can just rely on the value of 'User-Agent' sent via HTTP.
jshin: i'm betting this is a marketting bug, note that you can't really use the useragent to do what you think. the useragent lets google find out when a mozilla browser visits google. it doesn't let google find out when someone is using mozilla's search feature. there's a difference, and i'm betting that's what they're trying to measure.
Yeah, I figured that. I'm closing this bug as invalid. Anyway, we should 'fix' bug 269469.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.