FYI: Firefox only uses TLSv1.0 (see [1]), while Chrome can use up to TLSv1.1 (see [2]).
If both Firefox and Chrome trigger the issue without no-tlsv11/12 option, then the issue can be triggered with TLSv1.0 for sure. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=733647 [2] http://code.google.com/p/chromium/issues/detail?id=90392
