aws.amazon.com: breakage
Closed this issue · 3 comments
chesha1 commented
stephenhawk8054 commented
@gorhill There's a removeparam
filter without value
||amazonwebservicesinc.tt.omtrdc.net/m2/amazonwebservicesinc/ubox/raw$xhr,3p,removeparam,domain=aws.amazon.com
from this issue: uBlockOrigin/uAssets#21446
Could it cause issue with DNR?
Nope, I think it's the redirect-rule
/web-vitals.$script,redirect-rule=noopjs,domain=amazon.com
Weird, I changed to /web-vitals.$script,redirect=noopjs,domain=amazon.com
in local build but it still can't redirect.
The redirect
ruleset still has
{"action":{"redirect":{"extensionPath":"/web_accessible_resources/noop.js"},"type":"redirect"},"condition":{"initiatorDomains":["amazon.com"],"resourceTypes":["script"],"urlFilter":"/web-vitals."},"id":15617,"priority":1},
but looks like it can't override
{"action":{"type":"block"},"condition":{"urlFilter":"/web-vitals."},"id":6233},
in main
ruleset?
It only works when I add :1
to it /web-vitals.$script,redirect=noopjs:1,domain=amazon.com
. Looks like because the priority
goes up to 2
?
gorhill commented
My mistake, I assumed default priority was 0 and now I see it is 1, so the redirect won't override the block
rule as a result. I need to fix and publish a new version.
gorhill commented
Fixed in uBOLite_2024.8.21.996