The notion of providing "options" when passing in a URL is confusing. Unlike rules, URLs don't have a notion of options, but rather context around the request that would normally be matched against the options of a rule. It's currently entirely unclear how to format an "options" dictionary.
Ideally, we'll have a well defined interface with optional arguments:
content type of the request
top-level URL of the page on which the request occurred
etc
We can then map these to options. i.e., if the request URL and top-level URL don't have the same eTLD+1, we consider the request third-party and match it against third-party-only rules.
englehardt
commented
5 years ago
The notion of providing "options" when passing in a URL is confusing. Unlike rules, URLs don't have a notion of options, but rather context around the request that would normally be matched against the options of a rule. It's currently entirely unclear how to format an "options" dictionary.
Ideally, we'll have a well defined interface with optional arguments:
We can then map these to options. i.e., if the request URL and top-level URL don't have the same eTLD+1, we consider the request
third-partyand match it againstthird-party-only rules.