[INVALID] NoScript bit.ly issue

[exatto]

I've been having an error with bit.ly links for some time now. Whenever I click on a bit.ly link in twitter, the site doesn't load but shows something like this:



The weird thing is, if I reload the page immediately it comes back to the same screen. But after a few hours, sometimes days, when I reload again it puts me through to the intended webpage.

Anyone have any idea how I can fix this?

Thank you.

[therube]

URL where it occurs?

Though thinking your seeing, 3.17 Q: Some pages display the little NoScript icon with one or more links on its left side. I thought this could be disabled by unchecking "Show placeholder", but it's still shown... How do I make it go away?

[exatto]

These are a few example links which are all not working for me: https://t.co/gx1Trims, https://t.co/LirkFmVu and https://t.co/oCjqomb8. As you can see it are all t.co (twitter) links redirecting through bit.ly. Other t.co links work without any problems. The weird thing is that when I try to reload them on a later time they'll eventually redirect.
I've tried setting the noscript.jsredirect option to true, but the only thing it does is hide the link.

Thank you.

[Giorgio Maone]

All those links are working just fine for me.
How about a clean profile with just NoScript installed?
If that works for you, could you try Standard Diagnostic to look for any extensions conflict?

[exatto]

After selectively disabling and enabling addons, I've found the culprit to be CsFire: https://addons.mozilla.org/en-US/firefox/addon/csfire/.
I'm sorry that I thought it was due to NoScript, I was put off by the logo next to the redirect links.
I'm contacting the makers of CsFire now for extra support.

Anyway thank you for the great support and keep up the good work!

[Thrawn]

After selectively disabling and enabling addons, I've found the culprit to be CsFire: https://addons.mozilla.org/en-US/firefox/addon/csfire/.
I'm sorry that I thought it was due to NoScript, I was put off by the logo next to the redirect links.
I'm contacting the makers of CsFire now for extra support.

I've tried CsFire a while ago, but had trouble with it, eg I couldn't seem to successfully whitelist a site. Anyway, I settled on RequestPolicy instead - blocking cross-site requests, not just anonymizing them.

If you really want to anonymize requests by default, then ABE can do that in a less buggy fashion, with the following rule (at the end of the USER ruleset):

Code: Select all

Site *
Accept from SELF++
Anonymize

And put exceptions above it as needed, eg:

Code: Select all

Site .ytimg.com
Accept from SELF++ .youtube.com
Anonymize