Unresponsive script

[Giorgio Maone]

Sorry, my fault.
Must be:

Code: Select all

^@http://([a-z]+)\.google\.(?:[a-z]{1,3}\.)?[a-z]+(?:/|$)

(notice the "@" after the "^", rather than before).

Good luck and let me know

[grahamt]

OK, I'll change it to that. I'll get back to you once I've given it an extended trial. I'll let you know straight away if it doesn't work.

[grahamt]

Well, good news, have been running with the revised and corrected rule all day and not one incidence of the previously experienced errors. Many thanks.

Just one question, the format of the rule that you got wrong: was the format invalid? If so, shouldn't NoScript have reported the rule as invalid in format?

[Giorgio Maone]

Well, good news, have been running with the revised and corrected rule all day and not one incidence of the previously experienced errors. Many thanks.

Just one question, the format of the rule that you got wrong: was the format invalid? If so, shouldn't NoScript have reported the rule as invalid in format?

It was not an invalid regular expression, just it didn't do what it was meant to do.

[grahamt]

OK, still good news and the iGoogle page itself seems to post far, far quicker. I suppose that's because NoScript isn't doing any of the checking that previously slowed it down. As I understand it, the effect of the new rule is to turn off XSS checking for the Google website. Whilst that may have solved the immediate problem, is that wise? I thought that's why I installed NoScript in the first place!

[Giorgio Maone]

As I understand it, the effect of the new rule is to turn off XSS checking for the Google website. Whilst that may have solved the immediate problem, is that wise?

The effect is actually turning off XSS checks for requests originated by the iGoogle startup page.
This is less safe than default setup, but much safer than turning off XSS completely or uninstalling NoScript.

[Giorgio Maone]

Could you try latest development build (1.9.9.32), removing the XSS exception?
InjectionChecker should be about 5 times faster on that kind of nested URIs, therefore your problem may be fixed.