[RESOLVED] NoScript blocks site in Whitelist

[Cheech]

Hello:

NoScript version 1.9.3.3 on Windows/XP/SP3

NoScript is blocking a site that is in my white list from executing Java. The site URL is http://vyew.com/. It is Webex like freeware (collaboration, desktop sharing, ...) and can be easily accessed and used by just registering. It does not install any software.

The site tests to make sure Java is available and gives an error message if it is not, which I received. The site is in my white list. If I globally disable NoScript and refresh the current page the site then works as expected. I have screen shots in a Word document but I do see how to attach the file and do not know how to inset them as images.

Ciao

[Giorgio Maone]

As far as I can see they use Flash, rather than Java.
It works for me: could you try to forbid vyew.com, then allow it back?

[Cheech]

Yes they do use Flash and apparently they also use Java. The Desktop Sharing component needs Java 1.6 which I didn't have on my system at the time so I upgraded it. The problem appeared some time after I did the upgrade. I should had mentioned all of this in my first post but I hadn't connected the dots on it possibly being related to the upgrade. I had encountered a different error where they couldn't detect that both Flash and Java were even installed on my system even though previously (prior to the Java upgrade) they detected both. At the time that did not seem to have anything to do with NS.

Anyway, I did as suggested (forbid then allow) and that seems to have corrected the problem at least to this point. I haven't tested everything yet but will do so and report back. Thanks for your help.

[GµårÐïåñ]

By any chance you have apply to trusted sites enabled?

[Cheech]

No I do not.

[GµårÐïåñ]

Then only other thing I can think of might be a conflict of some kind with another extension, have you tried resetting NS (after you export your whitelist so you can restore it) to make sure nothing is corrupted or stuck? Otherwise, try the standard diagnostics to rule out extension conflicts. As Giorgio stated, it seems to work, so let's see if we can figure out what's causing it.

[Cheech]

OK, I'll plan to do that once I can confirm the problem still exists.

As I noted above, once I did the forbid then allow routine the error disappeared. I confirmed today that I can really share my desktop so until (and if) the problem returns I will not do anything. I'll post again if it does occur and after I have collected the information requested.

Thanks all.

[GµårÐïåñ]

Sounds like a plan, keep us posted should it return.