Reply to thread

I've never seen this reported before, but doing some Googling indicates that the error function (where that line points to) must've been called without a server response. It looks like we should be able to check the readyState as well, which I think should prevent this from happening.