I have the same issue and it works fine with Chrome. From what I have found it is related to:
"This seems to be caused by a bug fix for the BEAST (Browser Exploit Against SSL/TLS) attack that the server doesn't handle."
Not sure how to fix this yet.
