The Real Blogger Status

Those Blogger blog owners who continue to use an older browser, and who have decided to check out the New Blogger GUI (2011) , may be familiar with the ominous advice Your browser is no longer supported by Blogger. Some parts of Blogger will not work and you may experience problems. If you are having problems, try Google Chrome. Some of you have opted to check out the New GUI, even when faced with the warning - and have been faced with a cold reality. I mistakenly clicked on the "Try the updated Blogger interface" link and now I just have a blank screen because my computer is outdated. Having seen a steady flood of the latter complaint, in Blogger Help Forum: Something Is Broken , Blogger recently released a non GUI Recovery process . www.blogger.com/opt-in-new-ui.g?useNewUi=false

We've been noting Error 400 reports , from people trying to use Blogger, for some time. Tonight, we're seeing a significant increase in the reporting level for this symptom. Blogger Support has fixed the problem . We've rolled back the change that caused issues you have observed, so you should be able to clear the cookies for www.blogger.com and fix the problem.

In terms of vague, monolithic error messages, I don't know of a more mysterious error. The referential WikiPedia article List of HTTP status codes tells us simply The request contains bad syntax or cannot be fulfilled. The relevant clue here may be that "4nn" errors are "Client Request" errors. If you Google for information, you'll get dozens of supposed explanations . Here, a sample: About.com: 400 Bad Request Error Resolution ASP FAQ: Why do I get HTTP/1.1 400 Bad Request errors? CheckUpDown: HTTP Error 400 - Bad request The problem with the Error 400 is that it is seen in very low volume - maybe 1 or 2 reports / week. It's consistent in volume - we simply don't see an affinity. If you're seeing this, first try one of the most universally prescribed nostrums in Blogger land - clear cache, cookies, and active logins , and restart the browser. An alternative would be to try using a different browser - if this helps, you could rule ou...