User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Clicking on [bookmarks] - [Firefox and Mozilla Links] - [Firefox Start Page] results in http://www.google.com/firefox/ url in address bar and 404 Not Found error (The requested URL /firefox/ was not found on this server.) being returned by Google. Reproducible: Always Steps to Reproduce: 1.Bookmarks 2.Firefox Mozilla Links 3.Firefox Start page Actual Results: http://www.google.com/firefox/ url in address bar and 404 Not Found error (The requested URL /firefox/ was not found on this server.) returned by Google Expected Results: http://start.mozilla.org/firefox/ should load as indicated in the Propeties Dialog box This is occuring with the saferfox theme. I have not tested with other themes. I will select severity as Major although I consider it to be a Critical issue when trying to convince new users about security. Loading a url not specified in the properties dialog could be serious risk. Therefore I will send a security email also to reference this bug.
I have switched back to the default theme and still produce the same exact results.
Version: unspecified → 1.0 Branch
Not a security exploit, clearing confidential flag. The redirection is intended, Google is hosting the Firefox start page. Somehow your prefs got an extra '/' at the end, and that's being copied as part of the redirect. "http://www.google.com/firefox/" is not found, the real start page is "http://www.google.com/firefox" Remove the trailing slash in firefox/ from your prefs and it will work fine. I don't know how you got in this state, perhaps it was that way in an earlier version.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
You need to log in before you can comment on or make changes to this bug.