[DNR] Redirect rule does not allow applying other redirect rules to the resulting request #468
Labels
follow-up: chrome
Needs a response from a Chrome representative
follow-up: safari
Needs a response from a Safari representative
proposal
Proposal for a change or new feature
supportive: firefox
Supportive from Firefox
topic: dnr
Related to declarativeNetRequest
Problem
The current implementation in both Chrome and FF does not allow "chaining"
redirect
URLs.Here's the problem:
https://example.org/?utm_campaign=foo&fb_ref=bar
utm_campaign
parameter and the other one that removesfb_ref
.https://example.org/?fb_ref=bar
, however otherredirect
rules will not be applied to that new request.The problems of this approach are:
Inconsistency. Other DNR rules can be applied to the new request, the exception is only made for
redirect
.Inability to target specific URL parameters. For instance, in AdGuard URL Tracking filter some rules are generic and we can combine them into a single DNR rule, but there are some rules specific for a given website.
For instance, there's a rule for
bloomberg.com
:||bloomberg.com^$removeparam=in_source
. With the current implementation we'll need to merge generic rules with every "specific" rule to cover all parameters. But there still will be edge cases like this where merging would be more problematic:Proposal
The proposal is to allow applying other redirect rules to a request even if this request is a result of applying a different redirect rule.
The text was updated successfully, but these errors were encountered: