1405395 - blocklist.xml not being updated with new Mega.nz block

Status: RESOLVED FIXED

(Toolkit :: Blocklist Policy Requests, defect)

Description

[Jorge Villalobos [:jorgev] (he/him)]

The block in bug 1404290 isn't working correctly. After forcing a blocklist update ping (per https://wiki.mozilla.org/Blocklisting/Testing), I see blocklists/addons.json being updated with that block, but not blocklist.xml, which I believe is the one the Add-ons Manager currently uses.

This is blocking the full release of 56.

Comment 1

[Jorge Villalobos [:jorgev] (he/him)]

Who can look into this?

Comment 2

[Rémy Hubscher (:natim)]

I see it here: https://firefox.settings.services.mozilla.com/v1/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/56.0/

Comment 3

[[:philipp]]

the address my installation is pinging for the blocklist update is https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/56.0/Firefox/20170926190823/WINNT_x86-msvc/de/release/Windows_NT%2010.0/default/default/invalid/invalid/0/ where mega isn't included...

Comment 4

[Rémy Hubscher (:natim)]

However I do not see it here: https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/58.0a1/Firefox/20171003100226/Linux_x86_64-gcc3/fr/nightly/Linux%204.10.0-35-generic%20(GTK%203.22.11%2Clibpulse%2010.0.0)/default/default/invalid/invalid/0/

Jason do you know what could cause the mismatch?

Comment 5

[Jason Thomas [:jason]]

This should now be resolved. blocklists.settings.services.mozilla.com uses firefox.settings.services.mozilla.com (Cloudfront) as it's source and it was serving stale responses for some requests. I've manually issued a invalidation request on firefox.settings.services.mozilla.com and also purged all nginx cache for blocklists.settings.services.mozilla.com.