Hey guys, it's a server issue so not a lot I can do about it from my end. Jim O is always available and he is aware of the issue. Sorry for the bad gateways! ;-)
Ok, sorry for the double post, apparently a 502 does not in fact indicate a failure of a post(got it while posting that previous response, tried to post again.. apparently I didn't need to). Interesting.
Have now been unable to read any threads I have tried to look at, they are all 502'd. Trying with IE.
Works with IE... just not firefox. :/