by Di3S3L » Fri Jan 14, 2011 7:17 pm
I think it's not both, I tried adding my router's IP address to the 'noscript.doNotTrack.exceptions' string but the problem persists. I'll try your dev build next.
Details on my problem are about the same. I use a Linksys WRT120N, firmware version 1.0.05. Login through FireFox fails on this specific machine that I use, but not the other machines. All machines have NoScript and are fully updated. Pretty weird huh, you'd think that since all machines have the same browser and add-ons that you'd get the same problem across your network.
By failed login, I mean that the dialogue login box clears each time I enter the correct credentials, but if I press cancel, it gives me a 401 message: authentication failure or browser is not authentication capable.
Anyway, just thought you should know that it probably isn't the string that gives the workaround, but possibly the dev build.
[EDIT]
I read up on this thread some more, and the boolean noscript.doNotTrack.enabled toggled to false lets me access my router settings now. Mind you, I had the string noscript.doNotTrack.exceptions modified to my router's IP[192.168.1.1], so I don't know if it's a combination of both, or just the boolean that gives the workaround.
I think it's not both, I tried adding my router's IP address to the 'noscript.doNotTrack.exceptions' string but the problem persists. I'll try your dev build next.
Details on my problem are about the same. I use a Linksys WRT120N, firmware version 1.0.05. Login through FireFox fails on this specific machine that I use, but not the other machines. All machines have NoScript and are fully updated. Pretty weird huh, you'd think that since all machines have the same browser and add-ons that you'd get the same problem across your network.
By failed login, I mean that the dialogue login box clears each time I enter the correct credentials, but if I press cancel, it gives me a 401 message: authentication failure or browser is not authentication capable.
Anyway, just thought you should know that it probably isn't the string that gives the workaround, but possibly the dev build.
[EDIT]
I read up on this thread some more, and the boolean noscript.doNotTrack.enabled toggled to false lets me access my router settings now. Mind you, I had the string noscript.doNotTrack.exceptions modified to my router's IP[192.168.1.1], so I don't know if it's a combination of both, or just the boolean that gives the workaround.