-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Blocking meta refresh redirects #3378
Comments
The last work only on my local build, I did not commit the code yet. |
A new filtering class has been created: "static extended filtering". This new class is an umbrella class for more specialized filtering engines: - Cosmetic filtering - Scriptlet filtering - HTML filtering HTML filtering is available only on platforms which support modifying the response body on the fly, so only Firefox 57+ at the moment. With the ability to modify the response body, HTML filtering has been introduced: removing elements from the DOM before the source data has been parsed by the browser. A consequence of HTML filtering ability is to bring back script tag filtering feature.
Fixed with a9f68fe, will be in 1.14.23b3, the filter |
Works pretty well, thanks.
|
When I fixed #3069, the original intention was to allow to inject scriptlets before any other script tags on a page, thus removing the issue of potential race condition which could cause the inject scriptlets to not perform their duty. While I worked with the new Firefox 57 API to fix #3069, I realized that it would also be great to be able to support element removal using cosmetic filter-like syntax before the browser can even parse the source, since with #3069 the response data was already being modified. However there was no issue opened for such feature. So I will use the feature request here a posteriori in the release notes as the rationale for the new HTML filtering feature. |
how do i block meta refresh in chrome? i dont care if i have to block every single meta tag temporarily, im getting so frustrated with twitter refreshing on any cache or archive, im raging... |
For twitter, the |
how do i do that? |
My bad, I got confused and thought I was commenting on a uMatrix issue, somehow. So you are blocking javascript with Chrome's own javascript blocker? If so, you could instead block javascript on twitter with uBO, and enable javascript on twitter in Chrome settings. I tried it and it works fine for me, there was no redirection -- the |
This is a dircect followup of #226 as the main issue is not solved.
Describe the issue
I have javascript and cookies fully disabled. On some pages I get now a tracking redirect via meta refresh. This is no popunder so it is not addressed by this filter.
For example:
google.com does redirect to a tracking page where all links are converted to first link to google for redirect to other pages.
twitter does a endless redirect expecting a cookie for tracking is set (what I will never allow for twitter!) to mobile.twitter.com which shows nothing without javascript (What I also will never allow for twitter!)
One or more specific URLs where the issue occurs
Your settings
Your filter lists
Several, the issue is not related to existing filters.
Your custom filters (if any)
The last was a try to block it but failed, what means that I still see the tracking redirect.
The text was updated successfully, but these errors were encountered: