-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Classification of behind-the-scene requests in 1.47.0+? #2515
Comments
Apologies. I forgot to mention that you will need to select All in the drop-down page selector. |
Selecting All changes nothing, and anyways tabless network requests are always reported in the logger regardless of the drop down selector. |
I have no idea why it's not reproducing on your end. For some reason it didn't happen on first try, but I can clearly reproduce this with the STR provided on a vanilla Nightly profile. |
Ok I was filtering the logger output to see |
Should be fixed in the latest dev build, and I will include the fix in the next stable revision if all work as expected. |
It seems this was also related: uBlockOrigin/uAssets#11128 (comment) |
Prerequisites
I tried to reproduce the issue when...
Description
Requests previously classified as behind-the-scene in the logger are now (potentially) classified as first-party requests and have a partyness of
0,1
.A specific URL where the issue occurs.
N/A
Steps to Reproduce
This is just an example because I don't have a way to reliably trigger behind-the-scene requests other than closing a tab at the right moment since uBO became a WebExtension.
https://www.theguardian.com/
.Expected behavior
Two css requests to
https://assets.guim.co.uk/stylesheets/...
that were blocked by the rule* * 3p block
, and subsequent matching xhr requests to the same urls via behind-the-scene (mlgualtieri/CSS-Exfil-Protection#29 (comment)). The partyness of the latter should be(0,3) behind-the-scene ⇒ guim.co.uk
according to the logger in 1.46.0.Actual behavior
Two css requests to
https://assets.guim.co.uk/stylesheets/...
were blocked by the rule* * 3p block
, butassets.guim.co.uk
became the context for subsequent matching xhr requests. The partyness of the latter is also reported as(0,1) guim.co.uk ⇒ guim.co.uk
in the logger in 1.47.0.Meanwhile the context and partyness filter updates (which used to be considered behind-the-scene) are correctly
identified as
[uBO-uuid].moz-extension-scheme
and0,3
respectively.uBO version
1.47.0
Browser name and version
Firefox 110
Operating System and version
Windows 10
The text was updated successfully, but these errors were encountered: