Closed
Bug 639527
Opened 14 years ago
Closed 14 years ago
Include a last updated timestamp in the blocklist.xml
Categories
(Toolkit :: Blocklist Policy Requests, defect, P4)
Toolkit
Blocklist Policy Requests
Tracking
()
VERIFIED
FIXED
6.0.4
People
(Reporter: mossop, Assigned: jbalogh)
References
()
Details
Attachments
(2 files)
To facilitate bug 639524 I'd like the blocklist service to start including a timestamp of when it was last updated. This can either be the last time any changes were made to it or simpler just the time the xml was retrieved (the former is probably more complicated to program but caches better).
I'd see this appearing on the root blocklist element as:
<blocklist lastupdate="<ms since epoch>">
Comment 1•14 years ago
|
||
jbalogh just redid the blocklist in zamboni, so we can add this. It won't go live until the new blocklist does (after fx4).
Assignee: nobody → jbalogh
Priority: -- → P4
Target Milestone: --- → 6.0.3
| Assignee | ||
Comment 2•14 years ago
|
||
https://github.com/jbalogh/zamboni/commit/5cdbb9e
This looks like:
<blocklist xmlns="http://www.mozilla.org/2006/addons-blocklist" lastupdate="{{ now }}">
and will eventually show up on https://addons.allizom.org/z/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/4.0/.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•14 years ago
|
||
Ugh I just realised I made a big mistake here. The code that automatically pulls the blocklist into mozilla-central will always think that it has changed if the date is always changing. We either need to fix the code that does the import to ignore the date change (is that available somewhere for me to try to fix?), or make this date only change when the DB changes (hard I'm guessing), or back this out :(
| Assignee | ||
Updated•14 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 6.0.3 → 6.0.4
| Assignee | ||
Comment 4•14 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Comment 5•14 years ago
|
||
STR:
1. Add a new blocklistitem
2. Change extensions.blocklist.interval to 60 and reset app.update.lastUpdateTime.blocklist-background-update-timer
3. restart Firefox
4. Check blocklist.xml
expected behavior:
blocklist.xml has last updated timestamp
actual behavior:
blocklist.xml does not have the last updated timestamp
Updated•14 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 6•14 years ago
|
||
Your screenshot doesn't show the XML at all. I see a lastupdate attribute on the URL in comment 2.
| Assignee | ||
Comment 7•14 years ago
|
||
I'm not interested in what firefox does when it sees my blocklist.xml. All I care about is what's in https://addons.allizom.org/z/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/4.0/.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Comment 8•14 years ago
|
||
verified by checking the page source @ https://addons-next.allizom.org/z/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/4.0/
Status: RESOLVED → VERIFIED
Comment 9•14 years ago
|
||
| Reporter | ||
Comment 10•14 years ago
|
||
Why doesn't this seem to be live?
Comment 11•14 years ago
|
||
The blocklist code that is live is still running on PHP. We're waiting on QA to sign off on the new code in bug 640230 before enabling it. You should post there if it's blocking you on something.
Updated•9 years ago
|
Product: addons.mozilla.org → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•