Closed Bug 419750 Opened 13 years ago Closed 13 years ago

update safebrowsing server names

Categories

(Toolkit :: Safe Browsing, defect, P2)

defect

Tracking

()

RESOLVED FIXED
Firefox 3

People

(Reporter: dcamp, Assigned: dcamp)

Details

Attachments

(1 file)

Google is asking us to change sb.google.com -> safebrowsing.clients.google.com for safebrowsing requests.
Flags: blocking-firefox3?
OS: Mac OS X → All
Hardware: PC → All
Attached patch updates the servers that are ready.

The getkey server can't be switched yet, I'll leave this bug open until it can be.
Assignee: nobody → dcamp
Status: NEW → ASSIGNED
Attachment #305894 - Flags: review?(tony)
Attachment #305894 - Attachment is patch: true
Attachment #305894 - Attachment mime type: application/octet-stream → text/plain
Attachment #305894 - Flags: review?(tony) → review+
Attachment #305894 - Flags: approval1.9?
Comment on attachment 305894 [details] [diff] [review]
update server name

a=beltzner for 1.9
Attachment #305894 - Flags: approval1.9? → approval1.9+
Checking in firefox.js;
/cvsroot/mozilla/browser/app/profile/firefox.js,v  <--  firefox.js
new revision: 1.286; previous revision: 1.285
done
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Oops, forgot I was leaving this open.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Flags: blocking-firefox3? → blocking-firefox3+
Priority: -- → P2
Target Milestone: --- → Firefox 3
OK apparently they won't be updating they getkey server anytime soon.  Marking this bug fixed, we'll file a new one if they update the getkey server.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.