The Real Blogger Status

An HTTP trace is a very useful tool, for diagnosing and documenting connectivity issues, and many other blog problems. I use the Rex Swain HTTP Viewer , for this purpose. HTTP Viewer lets you package a given display, in the URL, so you can give simple instructions (accompanied by an unavoidably complicated link): Click on the link: http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://klarfamilylife.blogspot.com&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO And when the link is clicked, the necessary HTTP trace is displayed. There is no need to provide instructions how to actually enter the necessary values, on the HTTP Viewer home page, to generate the necessary display.

Some bloggers who subscribe to various blog feeds using Microsoft Outlook, and similar desktop client newsfeed readers, report problems with computers that are based on Local Area Networks and use local named resources. A coding error in the blog feed tracker, in the post footer, causes the URL, which should point to the Internet server "blogger.googleusercontent.com", to be interpreted as a request for local resource "//blogger.googleusercontent.com". The snippet of code, which should be provided as <div class="blogger-post-footer"><div></div><img width='1' height='1' src=' http: //blogger.googleusercontent.com/tracker/nnnnnnnnnnnnnnnnnnn-nnnnnnnnnnnnnnnnnnn?l=www.yoursite.com'/></div> instead is provided as <div class="blogger-post-footer"><div></div><img width='1' height='1' src='//blogger.googleusercontent.com/tracker/nnnnnnnnnnnnnnnnnnn-nnnnnnnnnn...

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...