Open Bug 1463377 Opened 7 years ago Updated 7 months ago

Migrate blocklist versionRange to JEXL filters

Categories

(Toolkit :: Blocklist Implementation, enhancement, P3)

61 Branch
enhancement

Tracking

()

Future

People

(Reporter: leplatrem, Unassigned)

References

Details

Once our whole user base will support JEXL (bug 1451031) we can migrate the `versionRange` field to JEXL expressions on the server side, and remove the custom target filtering code from bug 1458920
Component: Blocklist Policy Requests → Blocklist Implementation
Depends on: 1649872
Severity: normal → S3

The only remaining active use of versionRange is the Gfx blocklist, current production data at https://firefox.settings.services.mozilla.com/v1/buckets/blocklists/collections/gfx/records

Previously, it was also used in the plugin blocklist and extension blocklist v2. These are obsolete, however.

In bug 1649872, the Gfx blocklist got support for filter_expression, in Firefox 80 (and uplifted to 79 / ESR78).

Due to the root CA expiration (https://support.mozilla.org/en-US/kb/root-certificate-expiration), the only clients that can fetch new RS records are ESR 115.13+ and Firefox 128+. That means that there are no clients without support for filter_expression.

Would it be a good time to migrate to filter_expression for the Gfx blocklist, and remove the special versionRange logic from the Gfx blocklist?

Flags: needinfo?(mathieu)

Thank you for the background and context.

Would it be a good time to migrate to filter_expression for the Gfx blocklist, and remove the special versionRange logic from the Gfx blocklist?

Yes, definitely!

Flags: needinfo?(mathieu)
You need to log in before you can comment on or make changes to this bug.