Skip to main content

Blogger Commenting, CAPTCHA Screening, And Third Party Cookies

Many blog owners - or prospective blog readers - do not understand the significance of "third party cookies", in Blogger.

Recent changes in Blogger commenting, and setting changes by blog owners, possibly related to the new comment filters, have created a variety of problem reports which involve "third party cookies".

Blogger authentication cookies, which are created under "" and read under "" - or whatever non BlogSpot address the blog in question is published to - are affected by the "third party cookie" option. "Third party cookies", as with all cookies, are affected by filters which may be found in any section of a layered security policy.

This option is most commonly found in a browser filter setting.

It may also appear as a cookie or script filter, in some browser security add-ons, in any anti-virus, firewall, or "security suite" that runs on the computer, and in a network appliance which may be labeled as a "modem" or "router".

CAPTCHA ("word verification") screening does not, by its basic nature, require access to "third party cookies". Blogger commenting options, however, make access to the Blogger authentication cookies necessary.

The nature of the comment posting form is an additional issue. Originally, blogs which use an inline comment form ("Embedded below post") were affected by "third party cookie" filters.

Both "Full page" and "Pop-up window" forms run under "", and were not affected. If you don't believe me, examine the URL in the browser address window, with any comment form displayed.

A blog that uses an inline comment form is affected by two comment settings.

  • "Who Can Comment?" allows blog readers, other than members, to post comments.
  • "Show word verification for comments?", when selected by the blog owner, requires only non blog members to solve a CAPTCHA when posting a comment.

Both options require that a Blogger authentication cookie be accessed, in the scripts that build a blog page that includes an inline comment form. Taken in combination, there may be up to 8 different scenarios created by these settings.

If you can't comment on other people's blogs, or if various readers of your blog can't comment on your blog, and if the blogs involved use an inline comment form, chances are very good that "third party cookie" filters are part of the problem. This isn't an attempt by Blogger to hijack your browser, it's just the way authentication, and comment posting, work. And it's not a problem that Blogger can correct, by themselves.


Lorelei said…
I'm trying to check to make sure that I am not blocking third party cookies--although I'm not having trouble commenting (except at YouTube). However I can't find where this info is...can't find it under Options. I'm using Firefox 6.0.2 and haven't had it that long so I'm probably not looking in the right place. Do you have any info on that?
reply for Lorelei--
I had same problem.
Go to settings, then comments, and under SHOW word verification for comments? check the NO box, Now mine works.
Strange though, because the verification has worked for months for me.

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: