InformAction Forums

When I'm on Twitter with FF and NS enabled, some of the links do not work. Whereas if I disable NS or use IE (which doesn't have NS) the same links work. FF opens a new tab with an address for t.co and sits there like it is stuck in a loop. The message displayed on Twitter is "Sorry, but we couldn't find that link". Am I missing a setting in NoScript? I tried to several changes, either checking or unchecking a box and then setting it back. I also made sure t.co is in the Whitelist.

Please let me know what I should try. Everything else I use works great with NS. Thanks for a great product!

Does just clicking on t.co links from Twitter does not work or opening them in general?

What happens if you copy and then "Paste & Go" the following in the addressbar of an empty tab?

That does not work either. But if NS is disabled, then it works.

Same message ("Sorry, but we couldn't find that link")?

Strange because from what I see all the site tries to do is to redirect:

try disabling the t.co surrogate (set noscript.surrogate.t_co.sources to empty string)

Is the surrogate necessary, Giorgio? There's a meta refresh there.

al_9x wrote:There's a meta refresh there.

But inside a NOSCRIPT element so it won't work when "Forbid META redirections inside <NOSCRIPT> elements" is checked.

al_9x wrote:try disabling the t.co surrogate (set noscript.surrogate.t_co.sources to empty string)

How do I do that?

NateT wrote:

al_9x wrote:try disabling the t.co surrogate (set noscript.surrogate.t_co.sources to empty string)

How do I do that?

in about:config, change the value of "noscript.surrogate.t_co.sources" from "!@t.co" to "" (empty string, no quotes)

Also, should have included this all earlier:

NS ver = 2.1.2.6
FF ver = 6.0.0.4240
OS ver = Win 7 Pro 64-bit (if that matters)

dhouwn wrote:

al_9x wrote:There's a meta refresh there.

But inside a NOSCRIPT element so it won't work when "Forbid META redirections inside <NOSCRIPT> elements" is checked.

"won't work" would mean a silently blocked redirection, but an alert with a button to follow, seems adequate, and arguably preferable (a. knowing where one is redirected, b. I though it was a bug at first, since it was configured to block but wasn't)

al_9x wrote:

dhouwn wrote:

al_9x wrote:There's a meta refresh there.

But inside a NOSCRIPT element so it won't work when "Forbid META redirections inside <NOSCRIPT> elements" is checked.

"won't work" would mean a silently blocked redirection, but an alert with a button to follow, seems adequate, and arguably preferable (a. knowing where one is redirected, b. I though it was a bug at first, since it was configured to block but wasn't)

For the records, when they initially launched t.co there was no NOSCRIPT fallback, and that's why the surrogate had been included.

al_9x wrote:in about:config, change the value of "noscript.surrogate.t_co.sources" from "!@t.co" to "" (empty string, no quotes)

There is no such setting in about:config for me. Should I add it with an empty string?

So I added that setting with an empty value, enabled NoScript and it worked. Should that have been in there already?

Anyway, problem solved.

Thanks for the direction