InformAction Forums

I've recently set up a VM running a squid proxy on my local machine, and am finding a rather strange bug when firefox is set to use the proxy and noscript is running. I'm looking for some suggestions for how to troubleshoot this further -- can I enable extra logging, or some other way to figure out what's going on here?


The error I'm getting is that basically, when I set firefox's proxy settings to use the VM, Noscript gets confused and blocks all scripts even though I've previously had the sites whitelisted. I can't tell exactly what's happening, but the site doesn't show up in the menu of "allow" options properly either. Sometimes it appears in square brackets and greyed out / disabled. (Also, I have whitelisted the sites with RequestPolicy -- everything was working, and starts working again, when I don't use the proxy.) Example on google.com:



I should note also that I DON'T have any problems with noscript when running from within another VM on the same machine, or from firefox on a separate machine, even when using the same proxy VM. It appears to possibly be some weirdness relating to the network or addressing of the local VM, but I don't know how to investigate any further.

Any suggestions? I'm currently running the latest 2.3.5rc6 dev build, and before that had the latest stable version from addons.mozilla.org, I think that would be 2.3.5. Is there a way to find out what's going on in more detail?

First and easiest place to look would be Firefox Error Console (Ctrl+Shift+J, or Tools > Web Developer > Error Console), click "Errors", and copy any red Error messages and paste them here. Also please click "Messages", and post here any messages relating to NoScript.

The strange thing is, there were no errors or relevant messages.

However.... after some deeper digging, I've found the resolution: "It isn't a bug, it's a feature."

Somehow, I'd turned on "block all active content except over HTTPS when using a proxy". And, well, I was using a proxy, so it blocked the content. Wish I'd remembered that option existed before I started digging through the code!

Mark this one as resolved.

Will do, and thanks for reporting back. Glad it wasn't an actual problem.