Jan 4, 2014 09:39 PM
Sorry about that, I missed picking up on that.
Browser troubleshooting 101 to those that might be interested, I deal with a lot of clients that aren't sure where to focus on troubleshooting these sorts of problems, so hopefully this helps:
All the browser does is render whatever HTML/CSS it has been given. If it isn't given HTML to render, such as what is happening here, there is nothing any browser can do. There is a long list of reasons as to why the backend would paint out and not handle the HTTP request, none of the them browser related.
The only exception I can think of is in the old days when some web apps would need Microsoft ActiveX stuff and not handle non-IE browsers, but these sorts of days are thankfully mostly, if not completely behind us. With the vBulletin app, which drives this forum, there is definitely nothing special or unusual required that renders certain browsers incompatible.
The sorts of things a browser incompatibility can cause are pretty much funky renderings, stuff that looks ugly, sometimes even scrambled, etc. This is often due to incompatible CSS rules, and you'll see this most of the time in IE, and there will be consistent browser-specific problems until the code has been changed.
There are of course a number of things that can cause a browser to paint out entirely (e.g. corrupt application files), but these things will break access to all sites and are generally rare. Every once in a while one might also experience strange browser voodoo resulting in spinning beach balls, pages that stall, just weird stuff that is hard to reproduce (I've always experienced this in Safari more than Chrome or Firefox, I guess Safari just hates me), but none of these sorts of things result in an error message being served by the website, and are generally temporary and random.
In short, when a site is giving you a specific error message like this, don't waste your time messing around with different browsers, there isn't anything you can do except wait and try again.