Closed Bug 693389 Opened 12 years ago Closed 12 years ago

Update urlclassifier DB for Mozilla com->org move


(Toolkit :: Safe Browsing, defect)

Not set



Firefox 11
Tracking Status
firefox9 + ---
firefox10 + fixed


(Reporter: gcp, Assigned: gcp)



(Whiteboard: [mozmill-test-blocked])


(1 file)

After the move of all mozilla content from to, users going directly to will get the correct warning because that URL is in the DB.

However, people who go to directly to will not get a warning. This could cause confusion if they discover those pages for example due to a Google search.

Update the Urlclassifier DB to the new URL.
Assignee: nobody → gpascutto
Currently both of our Mozmill tests which check those pages are broken. We need an update of the database to get those fixed. Can we get some progress on the requested review please? Thanks.
Whiteboard: [mozmill-test-blocked]
Blocks: 662213
Comment on attachment 566212 [details] [diff] [review]
Patch 1. Update urlclassifier DB to .org domains

Review of attachment 566212 [details] [diff] [review]:

r+, but did you verify that no other tests are using in server-locations.txt?
Attachment #566212 - Flags: review?(dcamp) → review+
Blocks: 700607
>r+, but did you verify that no other tests are using in server-

There's this:

# This is here so that we don't load the default live bookmark over
# the network in every test suite.

Make a separate bug for it? Unlike SB tests, it prolly just uses the redirect without issues.
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 11
Verified fixed with Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0a1) Gecko/20111112 Firefox/11.0a1 and a fresh profile.
This bug fix appears to be breaking

Which we regularly use as AMO editors to test addons, more specifically themes.  Testing against about:blocked and about:certerror is not sufficient because the behavior isn't 100% the same.

Do I need to file a new bug to get these URLs fixed?
>This bug fix appears to be breaking

Can you explain what you mean? I don't understand.
Maybe it isn't this bug exactly, but ever since this morning going to the two links I mentioned above does not result in the proper warnings.
Please file a separate bug.
As mentioned above it works with a fresh profile. I haven't actually tested which files of an existing profile have to be removed to get Firefox showing up those warning pages.

Per your instructions, bug 707652 was filed.
Please nominate for consideration for FF9/10, noting any possible risks. com->org feels low risk to me though.
Comment on attachment 566212 [details] [diff] [review]
Patch 1. Update urlclassifier DB to .org domains

[Approval Request Comment]
Regression caused by (bug #): Reworking of the websites
User impact if declined: Users might inadvertently think the phishing protection no longer works
Testing completed (on m-c, etc.): Baked for several weeks in Aurora
Risk to taking this patch (and alternatives if risky): None known
Attachment #566212 - Flags: approval-mozilla-beta?
Blocks: 707652
Comment on attachment 566212 [details] [diff] [review]
Patch 1. Update urlclassifier DB to .org domains

[Triage Comment]
Simple .com -> .org switch for its-an-attack.html and its-a-trap.html. Approved for beta.
Attachment #566212 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Blocks: 906304
No longer blocks: 707652
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.