The channel classifier should consider redirects when tracking protection is disable and tracking annotations are enabled. So for example, if example.com loads an iframe on tracker.com which redirects back to example.com, that load should still be flagged as a tracker since it went through a tracking domain. When TP is enabled, this is not necessary since TP will cancel the channel and the redirect will never happen. This is how same-site cookies walks through the redirect chain for its check: https://dxr.mozilla.org/mozilla-central/rev/dfb15917c057f17e5143f7d7c6e1972ba53efc49/netwerk/base/nsNetUtil.cpp#2193-2209
baku, if you have free cycles, can you take a look at this?
We also need to check the case when: 1. example.com loads a resource from example.net 2. example.net redirects to tracker.com I just ran into problems in a test that was doing this and the resource did not appear to get annotated properly.
You need to log in before you can comment on or make changes to this bug.