Skip to main content

Your Computer, Your Browser, And Cookies

This month, we have had a few reports of problems logging in to Blogger, possibly involving the "cookies" which retain login information from one online session to the next.

Many security issues are deeply frustrating, to the folks who have to endure the problems. This becomes more frustrating, when you understand that the code from Blogger.Com has no choice in the matter. If Blogger.Com requires cookies (as most web sites do), and if cookies aren't being retained by the browser, the Blogger scripts can't function. And when you have a setting that's created under "" and read while your blog is being accessed (under "" or whatever non BlogSpot domain your blog is published), you'll need third party cookies enabled.

The really frustrating issue is that many security products, constantly "evolving" thanks to economic pressure (free enterprise competition) and security pressure (never ending hacking attempts), are constantly adding to their functionality. What used to be called a "personal firewall" (a network level protection) is now called a "security suite". Ditto for what used to be called "antivirus protection" (an application level protection) is likewise called a "security suite". Any of these may now contain cookie or script restrictions, and cause your problem.

Complicating this matter is some security suites may bind with some browsers, but not all, and may not consistently provide the same level of protection with all browsers.

If you are seeing this problem with one browser, but not another, I seriously suggest that you examine your computer for any security protection, and for any recent changes. Only you know what security products have been added to your computer. And any of them might have settings to block (or permit) cookies and scripts.

The bottom line, though, is that Blogger scripts don't manage the cookies, they only read and write them. If you have a problem, you visit Blogger Help Group, and you find only a couple (or no) other posts about your problem, consider carefully whether Blogger is undeniably the primary cause of your problem.

>> Top


Melisa said…
Thanks for posting this.

I have just deleted my new blog because of this cookie problem. I wonder why WordPress and Weebly don't have such problems, and I wonder why it happens now when I haven't changed our Internet setting. I am able to log into my Google email, but I have a frustrating difficulty previewing the edited posts every now and then. Sometimes they allow you to preview it, but most of the time no. I am thinking if my site has been hacked or what.

Another thing, I couldn't contact Blogger support. They just kept me going around in circles, so I wasn't able to tell them the problem.

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: