Closed
Bug 369012
Opened 18 years ago
Closed 17 years ago
split client name and version number into separate query params
Categories
(Toolkit :: Safe Browsing, enhancement)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
FIXED
People
(Reporter: tony, Assigned: tony)
Details
(Keywords: verified1.8.1.4)
Attachments
(1 file)
3.42 KB,
patch
|
marria
:
review+
dveditz
:
approval1.8.1.4+
|
Details | Diff | Splinter Review |
For logging reasons, it's easier if we have the client name and the app version in separate query parameters when making update and lookup requests.
Assignee | ||
Comment 1•18 years ago
|
||
Specifically, this changes the update url to be update?client=Firefox&appver=2.0.0.1& or update?client=navclient-auto-ffox&appver=2.0.0.1& And it changes the lookup url to be lookup?client=Firefox&appver=2.0.0.1& or lookup?client=navclient-auto-ffox&appver=2.0.0.1&
Attachment #253676 -
Flags: review?
Assignee | ||
Updated•18 years ago
|
Attachment #253676 -
Flags: review? → review?(marria)
Comment 2•18 years ago
|
||
Comment on attachment 253676 [details] [diff] [review] split {moz:client} and {moz:version} Looks good to me
Attachment #253676 -
Flags: review?(marria) → review+
Assignee | ||
Comment 3•18 years ago
|
||
On trunk. Checking in app/profile/firefox.js; /cvsroot/mozilla/browser/app/profile/firefox.js,v <-- firefox.js new revision: 1.169; previous revision: 1.168 done Checking in components/safebrowsing/content/globalstore.js; /cvsroot/mozilla/browser/components/safebrowsing/content/globalstore.js,v <-- globalstore.js new revision: 1.15; previous revision: 1.14 done
Assignee | ||
Updated•18 years ago
|
Flags: blocking1.8.1.3?
Assignee | ||
Updated•18 years ago
|
Attachment #253676 -
Flags: approval1.8.1.3?
Comment 4•17 years ago
|
||
Blocking to keep on the radar for now. How is the trunk version working? Happy with the patch? Does the server back-end handle getting two different formats (new and old) at the same time?
Flags: blocking1.8.1.4? → blocking1.8.1.4+
Assignee | ||
Comment 5•17 years ago
|
||
(In reply to comment #4) > How is the trunk version working? Happy with the patch? Does the server > back-end handle getting two different formats (new and old) at the same time? The server handles both (new and old) formats. It's working fine on trunk right now.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 6•17 years ago
|
||
Comment on attachment 253676 [details] [diff] [review] split {moz:client} and {moz:version} approved for 1.8.1.4, a=dveditz for release-drivers
Attachment #253676 -
Flags: approval1.8.1.4? → approval1.8.1.4+
Assignee | ||
Comment 7•17 years ago
|
||
on branch Checking in app/profile/firefox.js; /cvsroot/mozilla/browser/app/profile/firefox.js,v <-- firefox.js new revision: 1.71.2.82; previous revision: 1.71.2.81 done Checking in components/safebrowsing/content/globalstore.js; /cvsroot/mozilla/browser/components/safebrowsing/content/globalstore.js,v <-- globalstore.js new revision: 1.1.2.11; previous revision: 1.1.2.10 done
Keywords: fixed1.8.1.4
Comment 8•17 years ago
|
||
Verified on: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.4pre) Gecko/20070506 BonEcho/2.0.0.4pre Used livehttpheaders and searched for update and lookup urls which now look like: http://sb.google.com/safebrowsing/update?client=navclient-auto-ffox&appver=2.0.0.4pre... http://sb.google.com/safebrowsing/lookup?sourceid=firefox-antiphish&features=TrustRank&client=navclient-auto-ffox&appver=2.0.0.4pre...
Updated•17 years ago
|
Keywords: fixed1.8.1.4 → verified1.8.1.4
Updated•10 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•