PDA

View Full Version : Firefox 3.6 Users Occasionally Getting Security Token Errors


pete
03-19-2010, 09:19 PM
This is actually a Firefox problem, not a vBulletin problem. It's also platform independent (i.e. doesn't matter if you've got a PC, Linux box, Mac, etc.).

The original problem was posted on the vBulletin forums at http://www.vbulletin.com/forum/showthread.php?340825-Firefox-3.6-users-getting-Security-Token-Errors-when-posting-on-forums

The corrected description was posted to the Mozilla (the folks that make Firefox) at http://support.mozilla.com/en-US/forum/1/565399

The work-around is to use a different browser (even FF 3.5.7). There is currently no planned fix for this issue, according to Mozilla.

Another work-around is:

Open about:config in FF and put javascript.options.jit.content in the filter. Double click on the value to change it from true to false and see if that resolves the issue. It seems to have worked for me. But it does make FF slower.

FWIW, I've only had this happen to me once and I've had no reports from any WooF member that's havening a problem.

Gandalfe
03-19-2010, 09:38 PM
Uploaded 3.6; thanks Pete!

saxhound
03-19-2010, 09:39 PM
I'm using 3.5.8. No errors so far. I do have FlashBlock, NoScript and TACO (Targeted Advertising Cookie Opt-out) enabled.

pete
03-19-2010, 11:26 PM
Uploaded 3.6; thanks Pete!
I hope you mean, "I won't use 3.6; thanks Pete!"

I'm using 3.5.8. No errors so far.
I wasn't aware that there was a 3.5.8. Nice find!

I've been using the Google Chrome beta for the last bit, so I haven't really kept up with things Firefox. I can say that I had occasionally been getting errors with FF 3.6 Portable, but I chalked that up to "portable edition", not "problem with FF" (which it is).

Gandalfe
03-19-2010, 11:36 PM
I hope you mean, "I won't use 3.6; thanks Pete!"Nope, I test this stuff for grins and giggles.

saxhound
03-19-2010, 11:48 PM
3.5.8 is still available although I had to dig a bit.

http://www.mozilla.com/en-US/firefox/all-older.html

tictactux
03-20-2010, 12:06 AM
FWIW I'm running FF 3.6 (Portable) and haven't noticed such issues.

Guess I'm lucky. <touches wood>

pete
04-06-2010, 08:43 PM
Allegedly, the problem still occurs in FF 3.6.2, but 3.6.3 is now available. There's also a Java update (19).

The Google Chrome beta seems to work juuuust fine.