[RESOLVED] Greasemonkey XMLHttpRequest

[mari]

Hello everybody.

I have installed a Greasemonkey user script called UnShortenEmAll ( http://userscripts.org/scripts/show/64333 ) and it worked fine for several months.
This script resolves short URLs like bit.ly or tinyurl.com through GM_xmlhttpRequest.
However with recent NoScript versions 1.9.9.77 and 1.9.9.79 resolving short URLs stopped working and NoScript throws an error in the Error Console.
For exmaple:

Code: Select all

Fehler: [Exception... "'NoScript aborted redirection to http://www.rp-online.de/politik/deutschland/Medienwissenschaftler-entlastet-Tauss_aid_860287.html' when calling method: [nsIChannelEventSink::onChannelRedirect]"  nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]

for the link http://bit.ly/adjAWn on http://twitter.com/Tauss

When I revert NoScript back to version 1.9.9.74 everything works fine.
Is there a way to allow Greasemokney’s XMLHttpRequest in NoScript or is there a way to work around this?

[Giorgio Maone]

Thanks for your report. I'm investigating.

[Giorgio Maone]

Thanks for your report. I'm investigating.

BTW, are you double sure 1.9.9.74 works? the stuff I've found as the cause (which will be fixed in the upcoming 1.9.9.80) has not changed for a while...

[mari]

Thanks for your report. I'm investigating.

BTW, are you double sure 1.9.9.74 works? the stuff I've found as the cause (which will be fixed in the upcoming 1.9.9.80) has not changed for a while...

Yes, definitely.
I created a new Firefox profile, installed Greasemonkey + user script → short URL resolution worked fine.
Then installed NoScript 1.9.9.79 and short URLs were not resolved any more and lines like

Code: Select all

Fehler: [Exception... "'NoScript aborted redirection to http://www.heise.de/tp/blogs/5/147656' when calling method: [nsIChannelEventSink::onChannelRedirect]"  nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)"  location: "<unknown>"  data: no]

started showing up in Error Console.
Then I installed Noscript 1.9.9.74 ( through AMO) and everything worked again.

[mari]

This problem has been solved with version 1.9.9.80.
Thank you for all your work, Giorgio!