Open maricn opened 4 years ago
I noticed something similar a while ago on this page: https://www.wetteronline.de/wetter/berlin Following any link now on the page completely breaks it.
We can’t connect to the server at c-6rtwjumjzx7877x24bbbx2ebjyyjwtsqnsjx2eijundefined.
I noticed something similar a while ago on this page: https://www.wetteronline.de/wetter/berlin
We can’t connect to the server at c-6rtwjumjzx7877x24bbbx2ebjyyjwtsqnsjx2eijundefined.
@Skypodo: Those c-6rtw... URIs really look like the (wrong)doing of some rogue extension. Could you try disabling all your extensions except NoScript and check whether this issue persists?
@maricn: I cannot reproduce. Does the problem persist in latest NoScript versions? If it does, could you please share your NoScript Optios>Export configuration file? Thanks!
@hackademix The problem persisted with every addon disabled except for noscript. However, I tried turning off Firefox protection mechanism
(setting it to standard) and this did the trick. After some tests, it's the checkbox Tracking content
enabled on all sites (level 2 block list) that caused the issue.
Having only noscript or FF protection activated works fine but both at once doesn't.
I don't experience this problem anymore (it went away a while ago, iirc) on Firefox 73.01b and NoScript 11.0.3. Couldn't reproduce it now, and I also tried meddling with suggested Firefox protection settings.
On some websites instead of seeing a list of domains, some appear as TLD
com
like the third one on the screenshot below. When I enable it, the website works, however when I restrict it, seems like the restrictions apply across that matching TLD.Interesting here is that I already had these google related
.com
s below as untrusted, so it recognized them and applied rules accordingly as expected, like handling subdomains.My setup:
Examples: https://www.residentadvisor.net/ https://electricsheep.org/ ...