You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This extension failed to redirect a network request to https://s7.addthis.com/js/300/addthis_widget.js#pubid=tenthamendment because another extension (uBlock Origin) redirected it to chrome-extension://cjpalhdlnbpafiamejdnhcphjbkeiagm/web_accessible_resources/af3c919ee9a3d97f5dedaf2f8bec146a.javascript?secret=qqesz4qhqw5h.
Reacted by Ruben Torres L, herbzacz, Nibkat, CHAN, Chak Shing, Antonín Boušek, Dominik Menke, Léo Colombaro, Henrique Jung, Instagit, Rick and 118 more
I'm getting the same, in my case with a Google Analytics URL.
Appeared today with version 2018.2.26
This extension failed to redirect a network request to https://www.google-analytics.com/analytics.js because another extension (uBlock Origin) redirected it to chrome-extension://cjpalhdlnbpafiamejdnhcphjbkeiagm/web_accessible_resources/59fb24a2d12455d15bea20980e8a6801.javascript?secret=jblm6nqcej3g.
As an enhancement for HTTPS Everywhere, we might take resources.txt and use it to create exceptions for the various rewrites it does. For example we could add a checkbox that says "Exclude uBlock Origin rewrites" which, if checked, will not rewrite the items in resources.txt, and instead let uBlock Origin handle them.
I'm not saying this is a good idea to do, but it's something that could be done.
Reacted by James W Mann, Robbie Clarken, noblepirate, volcbs, Igor, Guillaume Simard, Florian Freudiger and Travis Eminhizer
I would appreciate this 'resources.txt' as exeptions, because honestly I don't want https everywhere to be redirecting me to tracking sites I explicitly block with ublock; the way it works now, trackers totally being blocked from loading, is the preferred scenario. I just want the ! to disappear making me think there are 'actual' problems with https on the site I am visiting.
Reacted by Mykyta Polishchuk, Guillaume Simard, Florian Freudiger and Kory Schneider
@terrorist96@blackhelicopters @ariksc @mystica555 Can you all please edit your comments to provide a URL where you go to see the problem? Not the error from the developer console, but the URL in your browser's address bar.
we might take resources.txt and use it to create exceptions for the various rewrites it does
In that case resources.txt is not the right place for this, that would rather be the filters themselves, those with the redirect= option in any of the filter lists in https://github.com/uBlockOrigin/uAssets/tree/master/filters. There is a lots of these, and these lists are constantly edited. For the specific case here, this would be this filter:
Why is this issue popular suddenly? Did something change recently in uBlock Origin?
I wondered. uBO has supported redirection since quite a while now, to data: URIs. However in a recent release uBO will redirect to web accessible resources instead of data: URIs. This has changed to solve long standing issue gorhill/uBlock#2823. Not sure whether this is what is causing more reports about this -- redirecting to data: URIs was also causing such conflicts before (as pointed out at old issue gorhill/uBlock#1170).
All of the reports here so far are reporting redirects to something under web_accessible_resources, so the recent uBlock Origin change may be related. But it sounds like these reporters should have seen the same error before, except it would have been to data: instead of web_accessible_resources, right?
@gorhill do you have statistical data on how often each of these patterns are matched in uBlock Origin? I'm wondering if we can avoid conflicts in a comprehensive but not complete way. We may be able to avoid the vast majority of conflict events in this way.
@Hainish If @gorhill doesn't have statistical data, then at least based on the comments here and gorhill/uBlock#3639 , specific handling for Google Analytics would take care of a lot of cases.
I added a partial revert of the fix to gorhill/uBlock#2823 (which is what the redirection to "web accessible resources" was fixing). uBO will avoid to redirect to a "web accessible resource" and instead redirect to a data: URI when the two following conditions are present:
uBO is running in a Chromium-based browser
The URL to redirect is a non-secure http: one (i.e. one which HTTP-Everywhere will likely want to redirect)
Reacted by Michael Scholtz, Adam Hirst, equinox, Hugo Gruson, cowlicks and ExE Boss
@gorhill it's hard to track as it seemingly happens at random. But today I caught it blocking something on Amazon:
This extension failed to redirect a network request to https://g-ecx.images-amazon.com/images/G/02/kindle/merch/2017/ACC/Promo/ACCBundles//UK_Bundle_Muscat_160X97.jpg because another extension (HTTPS Everywhere) redirected it to https://d1ge0kk1l5kms0.cloudfront.net/images/G/02/kindle/merch/2017/ACC/Promo/ACCBundles//UK_Bundle_Muscat_160X97.jpg
@lightheaded I am not aware of any filters in uBO which would want to redirect the URL your are mentioning.
Also, I find it surprising that HTTPS Everywhere would want to redirect a https: URL to another https: URL. The one related rule in HTTPS-E is to redirect from http: to https::
In any case, assuming you created custom rules to cause the behavior you are observing on your side, as said above, uBO fix with regard to HTTPS-E is a mitigation, i.e. this should take care of most conflicts, but this won't take care of conflict arising as a result of HTTPS-E redirecting a https: URL to another https URL (which I believe shouldn't be happening normally?)
It seems that chrome will stop notifying the users for extension conflicts in the dev channel.
This CL introduces the onActionIgnored event on the web request API which is
fired when an extension's proposed modification to a network request is ignored.
This happens in case of conflicts with other extensions. This should allow the
extensions to address conflicts as they like.
Also, we no longer notify the user in case of conflicts between extensions.
Activity
blackhelicoptersdotnet commentedon Mar 22, 2018
I'm getting the same, in my case with a Google Analytics URL.
Appeared today with version 2018.2.26
This extension failed to redirect a network request to https://www.google-analytics.com/analytics.js because another extension (uBlock Origin) redirected it to chrome-extension://cjpalhdlnbpafiamejdnhcphjbkeiagm/web_accessible_resources/59fb24a2d12455d15bea20980e8a6801.javascript?secret=jblm6nqcej3g.gorhill commentedon Mar 22, 2018
gorhill/uBlock#1170 (comment)
jeremyn commentedon Mar 22, 2018
@gorhill Your comment says "The resources used by uBO for redirection purpose are found in this file." but the linked file, https://github.com/gorhill/uBlock/blob/master/assets/ublock/resources.txt , doesn't exist anymore. Is there an equivalent?
gorhill commentedon Mar 22, 2018
I corrected the link, the resource files have been moved to a different repo since I wrote this comment: https://github.com/uBlockOrigin/uAssets/blob/master/filters/resources.txt.
jeremyn commentedon Mar 22, 2018
Thanks @gorhill .
As an enhancement for HTTPS Everywhere, we might take
resources.txtand use it to create exceptions for the various rewrites it does. For example we could add a checkbox that says "Exclude uBlock Origin rewrites" which, if checked, will not rewrite the items inresources.txt, and instead let uBlock Origin handle them.I'm not saying this is a good idea to do, but it's something that could be done.
mystica555 commentedon Mar 22, 2018
I would appreciate this 'resources.txt' as exeptions, because honestly I don't want https everywhere to be redirecting me to tracking sites I explicitly block with ublock; the way it works now, trackers totally being blocked from loading, is the preferred scenario. I just want the ! to disappear making me think there are 'actual' problems with https on the site I am visiting.
jeremyn commentedon Mar 22, 2018
@terrorist96 @blackhelicopters @ariksc @mystica555 Can you all please edit your comments to provide a URL where you go to see the problem? Not the error from the developer console, but the URL in your browser's address bar.
terrorist96 commentedon Mar 22, 2018
I'll try to post it if I come across it again. BTW, here's the PR Privacy Badger made to avoid this issue from occurring:
EFForg/privacybadger#1905
gorhill commentedon Mar 22, 2018
@jeremyn
In that case
resources.txtis not the right place for this, that would rather be the filters themselves, those with theredirect=option in any of the filter lists in https://github.com/uBlockOrigin/uAssets/tree/master/filters. There is a lots of these, and these lists are constantly edited. For the specific case here, this would be this filter:Which in plain language means: redirect all network requests for
addthis_widget.jsfromaddthis.comto a local, neutered version of the script.madusmacus commentedon Mar 23, 2018
This extension failed to redirect a network request to https://www.google-analytics.com/ga.js because another extension (uBlock Origin)
I have also had
This extension failed to redirect a network request to https://s7.addthis.com/js/300/addthis_widget.js#pubid=tenthamendment because another extension (uBlock Origin) redirected it to chrome-extension://cjpalhdlnbpafiamejdnhcphjbkeiagm/web_accessible_resources
jeremyn commentedon Mar 23, 2018
@gorhill Thanks. So it sounds like the logic for us might be: go through the files in https://github.com/uBlockOrigin/uAssets/tree/master/filters , look for filter lines that start with
||and includeredirect=, and add those partial-URLs to a list controlled by the checkbox I suggested earlier at #14961 (comment).Why is this issue popular suddenly? Did something change recently in uBlock Origin?
gorhill commentedon Mar 23, 2018
I wondered. uBO has supported redirection since quite a while now, to
data:URIs. However in a recent release uBO will redirect to web accessible resources instead ofdata:URIs. This has changed to solve long standing issue gorhill/uBlock#2823. Not sure whether this is what is causing more reports about this -- redirecting todata:URIs was also causing such conflicts before (as pointed out at old issue gorhill/uBlock#1170).jeremyn commentedon Mar 23, 2018
All of the reports here so far are reporting redirects to something under
web_accessible_resources, so the recent uBlock Origin change may be related. But it sounds like these reporters should have seen the same error before, except it would have been todata:instead ofweb_accessible_resources, right?42 remaining items
Hainish commentedon Apr 23, 2018
@gorhill do you have statistical data on how often each of these patterns are matched in uBlock Origin? I'm wondering if we can avoid conflicts in a comprehensive but not complete way. We may be able to avoid the vast majority of conflict events in this way.
jeremyn commentedon Apr 23, 2018
@Hainish If @gorhill doesn't have statistical data, then at least based on the comments here and gorhill/uBlock#3639 , specific handling for Google Analytics would take care of a lot of cases.
Paradoxum commentedon Apr 23, 2018
Is there any way to stop the (!) icon appearing at the very least for us end users? I'm getting this constantly and it's so frustrating.
gorhill commentedon Apr 24, 2018
I added a partial revert of the fix to gorhill/uBlock#2823 (which is what the redirection to "web accessible resources" was fixing). uBO will avoid to redirect to a "web accessible resource" and instead redirect to a
data:URI when the two following conditions are present:http:one (i.e. one which HTTP-Everywhere will likely want to redirect)lightheaded commentedon Jun 11, 2018
Just wanted to leave a note here that I'm still occasionally receiving this error on HTTPS Everywhere 2018.4.11
Hainish commentedon Jun 13, 2018
@lightheaded thanks, I've pinged Chromium again on this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=111700#c37
gorhill commentedon Jun 13, 2018
@lightheaded Having the exact web page where this happens would be useful to determine whether this is really the same exact issue identified here.
lightheaded commentedon Jun 27, 2018
@gorhill it's hard to track as it seemingly happens at random. But today I caught it blocking something on Amazon:
This extension failed to redirect a network request to https://g-ecx.images-amazon.com/images/G/02/kindle/merch/2017/ACC/Promo/ACCBundles//UK_Bundle_Muscat_160X97.jpg because another extension (HTTPS Everywhere) redirected it to https://d1ge0kk1l5kms0.cloudfront.net/images/G/02/kindle/merch/2017/ACC/Promo/ACCBundles//UK_Bundle_Muscat_160X97.jpggorhill commentedon Jun 27, 2018
@lightheaded I am not aware of any filters in uBO which would want to redirect the URL your are mentioning.
Also, I find it surprising that HTTPS Everywhere would want to redirect a
https:URL to anotherhttps:URL. The one related rule in HTTPS-E is to redirect fromhttp:tohttps::https-everywhere/src/chrome/content/rules/Images-Amazon.com.xml
Lines 31 to 32 in 73c41f6
In any case, assuming you created custom rules to cause the behavior you are observing on your side, as said above, uBO fix with regard to HTTPS-E is a mitigation, i.e. this should take care of most conflicts, but this won't take care of conflict arising as a result of HTTPS-E redirecting a
https:URL to anotherhttpsURL (which I believe shouldn't be happening normally?)jeremyn commentedon Jun 27, 2018
@gorhill FYI, there's an open issue #10843 to remove
https:->https:redirects where possible.cschanaj commentedon Aug 28, 2018
It seems that chrome will stop notifying the users for extension conflicts in the dev channel.
Ref
https://groups.google.com/a/chromium.org/forum/#!msg/extensions-reviews/YYn1etdxjgw/55bBFxxfCgAJ
https://developer.chrome.com/extensions/webRequest#event-onActionIgnored
Hainish commentedon Aug 28, 2018
Fantastic! Thanks for the heads up @cschanaj - we should definitely handle this event.
terrorist96 commentedon Nov 9, 2018
Can this be closed? Marked as fixed since Aug 24.
I haven't had this issue for a while.
Libbum commentedon Nov 9, 2018
Yep, nothing on my systems for a while too.