And the link http://www.mozilla.org/projects/bonecho/anti-phishing/ should be updated, although it is redirected to the current page.
Tony, it looks like you set up the original site. Would you or someone else be the right person to get this updated? Please see Bug 691719 as well.
I've forwarded on the request to the team at Google that owns the page. Hopefully someone will chime in. I'll check back in a day or so.
The safebrowsing team said that they would try to update it later this week.
It looks like the change has been made and it will go live in the next push. I'm not exactly sure when that will happen, but probably not on Friday or over the weekend.
Tony, I'm looking at the Report Web Forgery page , and it now looks like the image URL for the Firefox logo is broken. It points to a file that 404s . Also, this bug has the URL for the Report Incorrect Forgery Alert page, which is different . It also appears to have a broken CAPTCHA, and it still points to the old logo. Is that page still used? Thanks so much for your assistance!  https://www.google.com/safebrowsing/report_phish/?tpl=mozilla  https://gstatic.com/catalogs/firefox-logo.png  https://www.google.com/safebrowsing/report_error/?tpl=mozilla
Thanks for reporting! I'm told a fix is going to be pushed ASAP.
It looks like the logo has been updated. Does it look OK? Can we close this bug?
I still see the same problems as comment 5.
Assignee: nobody → tony
Status: NEW → ASSIGNED
What about now? Maybe it was only showing on VPN earlier. It shows up for me now from multiple places.
Tony, are you looking at the same page as we are?  It is embedding <https://gstatic.com/catalogs/firefox-logo.png> (due to the protocol-relative URL), which is a 404. However, if you change that URL to <http://gstatic.com/catalogs/firefox-logo.png>, it works. My question from Comment 5 still stands as well, as there are apparently two pages in play here.  https://www.google.com/safebrowsing/report_phish/?tpl=mozilla
Ah, you're right. Sorry, I was using the URL in the bug. I'll see if I can find out when the https version will be fixed.
Apologies for the delay. The Safebrowsing team has assured me the fix will be pushed on Monday.
Max says that this should be fixed now. It's working for me-- can you verify?
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
LGTM. Thank you Google folks!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.