Closed Bug 344063 Opened 19 years ago Closed 19 years ago

report phishing page should include the mozilla brand

Categories

(Toolkit :: Safe Browsing, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 2 beta1

People

(Reporter: tony, Assigned: tony)

References

Details

(Keywords: verified1.8.1)

Attachments

(2 files)

> > > When I select "Report a Phishing Website" from the Help menu, we end up > > > here: > > > > > > http://www.google.com/safebrowsing/report_phish/ > > > > > > There's an urgent desire to have the page that we land at Mozilla > > > co-branded w/ Google.
Flags: blocking-firefox2?
Target Milestone: --- → Firefox 2 beta1
blocking so we can triage it for today's respins
Flags: blocking-firefox2? → blocking-firefox2+
Spoke with Chris Beard and he'd rather the URLs point to mozilla.org to start with, and have those pages either use iframes or links to go over to the google pages. Changed the patch so that it uses: http://www.mozilla.org/projects/bonecho/anti-phishing/report_general/ http://www.mozilla.org/projects/bonecho/anti-phishing/report_error/ http://www.mozilla.org/projects/bonecho/anti-phishing/report_phish/ Chris says this blocks b1
Attachment #228688 - Flags: review?
Attachment #228688 - Flags: approval1.8.1?
(In reply to comment #3) > Created an attachment (id=228688) [edit] > changes report URLs to pages on mozilla.org > > Spoke with Chris Beard and he'd rather the URLs point to mozilla.org to start > with, and have those pages either use iframes or links to go over to the google > pages. Changed the patch so that it uses: > > http://www.mozilla.org/projects/bonecho/anti-phishing/report_general/ > http://www.mozilla.org/projects/bonecho/anti-phishing/report_error/ > http://www.mozilla.org/projects/bonecho/anti-phishing/report_phish/ Ok, iframes or links should work fine. Will we be using the urls in the previous patch (i.e., adding the client url parameter)? We need to make changes to the server to support this.
Oh, poop, yes, we should pass along the other parameters. Can you please whip up a patch that includes them?
Or wait, I think this patch will still automatically append them?
Let's use links from a mozilla.org hosted web page, aspirationally with .js to set and pass parameters to prepopulate form fields.
Attachment #228688 - Flags: review? → review+
Attachment #228688 - Flags: approval1.8.1? → approval1.8.1+
(In reply to comment #3) > Created an attachment (id=228688) [edit] > changes report URLs to pages on mozilla.org Landed on 181 branch. I added a ? to the end of the urls so appending params doesn't send it to a different directory. These urls will change when we localize properly (bug 343766).
Blocks: 344128
Well the current behavior is worse. There is an extra Mozilla branded page before you get to the actual report the phishing scam page. Clicking on the report this site as phishing link on that page takes you to the Google report a site page, but the URL is no longer filled in. Presumably this will all be sorted before the release?
Marking this one fixed. Filed bug 344551 for follow up issues.
Status: NEW → RESOLVED
Closed: 19 years ago
Keywords: verified1.8.1
Resolution: --- → FIXED
This doesn't seem to have landed on the trunk.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Do we want minefield to point to bonecho pages? Someone say "yes" and I'll go ahead and land on trunk.
Yeah, I'm OK with that for now. The final plan will be to have all users of the safebrowsing service pointing to mozilla.com pages ...
on trunk
Status: REOPENED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → FIXED
Tony, can we reopen this bug?
(In reply to comment #17) > Tony, can we reopen this bug? Maybe we can just use bug 346242 to track what needs to be done with regards to the report phishing pages?
That works. Thanks!
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: