Support wildcards

[dbfin]

Prerequisites

• [v] I performed a cursory search of the issue tracker to avoid opening a duplicate issue
  • Your issue may already be reported.
  • [v] I also searched the existing issues at https://github.com/gorhill/uMatrix/issues
• [v] This is not a support issue or a question
  • Support issues and questions are handled at /r/uMatrix
• I tried to reproduce the issue when...
  • uMatrix extension is wholly disabled or not installed
  • uMatrix is the only extension
  • uMatrix with default lists/settings
  • using a new, unmodified browser profile
• [v] I am running the latest version of uMatrix
• I checked the documentation to understand that the issue I report is not a normal behavior
• I used the logger to rule out that the issue is caused by my ruleset

Description

First, I have seen a few issues concerning wildcards, but they all talk about allowing subdomains, while I encountered the need for a broader use of wildcards. The issue is that there is a website, call it example.com, that uses a (larger number) of scripts and assets from websites of the form example###.net, where ### stands for a number. The numbers are all 3-digits, and there seems no real boundary on how small or large they can be. On top of that I do not want to allow everything from these sites, just say "passive" resources such as css, media and images, so I would have to add thousands of rules.

An alternative solution that would however require the use of wildcards would be to simply add 3 lines of the form

example.com example*.net ... allow

Now, I understand that implementing wildcards in their generality would eventually lead to new kinds of problems. For example, if for a subdomain there are currently several rules, the most specific wins, where a rule for a subdomain is considered to be more specific than a rule for the upper-level domain. With wildcards, for example, if I have conflicting rules for say cdn.*.com and *.example.com, then there is no obvious (at least at first) way to resolve the conflict for cdn.example.com.

But I was hoping, that given the above situation, someone could have a suggestion for my case specifically, or to the way of how indeed implement at least partial support for wildcards.

Thank you for your work!

A specific URL where the issue occurs

Steps to Reproduce

Try any wildcard rule -- they are not supported. Asterisks are interpreted literally.

Ruleset

Supporting evidence

Your environment

• uMatrix version: 1.4.0
• Browser Name and version: Firefox 80
• Operating System and version: Windows, Mac & Linux