Avoid Role Of Feedburner Password Protector
Sunday, May 5, 2013
Edit
Some Google products incorporate features that convey express usefulness, when applied to Blogger blogs.
FeedBurner has a feature, "Password Protector", which may travel useful, to newsfeed readers that back upward HTTP authentication. Within FeedBurner, nosotros convey the "Email Subscriptions" service - which does non back upward feed authentication.
Newsfeeds, published past times Blogger blogs, are supposed to travel publicly accessible.
H5N1 spider web log amongst designated readers will non hit a newsfeed. Blogger does non back upward authenticated newsfeeds.
To role Password Protector, hold off on the FeedBurner dashboard, nether the Publicize tab, for "Password Protector". Enter a Username together with a Password, together with hitting "Activate". But don't hit this, without knowing the downsides.
Password Protector uses a unmarried username / password combination. All spider web log readers volition role the same username.
FeedBurner warns us of possible problems, caused past times this service.
From what I tin move see, Blogger Reading List may ignore the authentication requirement. People may role Reading List, together with persuasion the spider web log feed, redirected through FeedBurner - fifty-fifty if non authorized.
We know, however, that e-mail subscriptions an HTTP trace of the feed from my examination spider web log http://techdict.nitecruzr.net, nosotros come across a symptom of the problem, amongst this option.
This appears to travel only a redirected spider web log posts newsfeed, targeting a FeedBurner published feed.
Here, nosotros come across a normal redirected spider web log posts feed.
But what happens, when nosotros seek to opened upward the feed?
The "HTTP Viewer" service does non back upward feed authentication (and solely plant amongst "HTTP:" protocol). And, nosotros come across the result.
It's possible that this characteristic volition travel useful, amongst feeds that are used exterior Blogger (noting the Reading List ability). If you're publishing a Blogger blog, however, you're non probable to larn whatsoever useful result.
Owners of #Blogger blogs, which role the FeedBurner "Password Protector" service, may notice that the service delivers less protection - together with to a greater extent than or less interference - other than the service mention suggests. It would likely travel best to avoid role of this service.
FeedBurner has a feature, "Password Protector", which may travel useful, to newsfeed readers that back upward HTTP authentication. Within FeedBurner, nosotros convey the "Email Subscriptions" service - which does non back upward feed authentication.
Your readers volition travel required to role newsreader or aggregator software that supports authentication to persuasion your feed.Some Google, together with non Google, services volition convey a problem, amongst a FeedBurner protected feed.
Newsfeeds, published past times Blogger blogs, are supposed to travel publicly accessible.
H5N1 spider web log amongst designated readers will non hit a newsfeed. Blogger does non back upward authenticated newsfeeds.
To role Password Protector, hold off on the FeedBurner dashboard, nether the Publicize tab, for "Password Protector". Enter a Username together with a Password, together with hitting "Activate". But don't hit this, without knowing the downsides.
Password Protector uses a unmarried username / password combination. All spider web log readers volition role the same username.
FeedBurner warns us of possible problems, caused past times this service.
Important: This service prevents our Email Subscriptions service from delivering e-mail updates from your feed, together with it volition too password protect your feed's content when redisplayed using our Headline Animator graphic. This graphic itself becomes password protected, which is undesirable if you lot wishing to role it to promote your site/feed. Therefore, nosotros recommend non using Headline Animator or Email Subscriptions, together with this Password Protector service, amongst the same feed.
From what I tin move see, Blogger Reading List may ignore the authentication requirement. People may role Reading List, together with persuasion the spider web log feed, redirected through FeedBurner - fifty-fifty if non authorized.
We know, however, that e-mail subscriptions an HTTP trace of the feed from my examination spider web log http://techdict.nitecruzr.net, nosotros come across a symptom of the problem, amongst this option.
http://techdict.nitecruzr.net/feeds/posts/default
http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://techdict.nitecruzr.net/feeds/posts/default&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
Sending request:
GET /feeds/posts/default HTTP/1.1
Host: techdict.nitecruzr.net
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7834.70.0) AppleWebKit/537.36 (KHTML, similar Gecko) Chrome/49.0.2623.112 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.28.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·302·Found(CR)(LF)
ETag:·W/"32e869db-18a9-4ccf-8ad9-dbded29f2b25"(CR)(LF)
Date:·Wed,·27·Apr·2016·15:04:06·GMT(CR)(LF)
Content-Type:·text/html(CR)(LF)
Server:·blogger-renderd(CR)(LF)
Expires:·Wed,·27·Apr·2016·15:04:07·GMT(CR)(LF)
Cache-Control:·public,·must-revalidate,·proxy-revalidate,·max-age=1(CR)(LF)
X-Content-Type-Options:·nosniff(CR)(LF)
X-XSS-Protection:·1;·mode=block(CR)(LF)
Location:·http://feeds.feedburner.com/ChucksTechWorld(CR)(LF)
This appears to travel only a redirected spider web log posts newsfeed, targeting a FeedBurner published feed.
Here, nosotros come across a normal redirected spider web log posts feed.
But what happens, when nosotros seek to opened upward the feed?
http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://feeds.feedburner.com/ChucksTechWorld&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=TXT
Sending request:
GET /ChucksTechWorld HTTP/1.1 HTTP/1.1
Host: feeds.feedburner.com
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7834.70.0) AppleWebKit/537.36 (KHTML, similar Gecko) Chrome/49.0.2623.112 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 172.217.0.14
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·401·Unauthorized(CR)(LF)
WWW-Authenticate:·BASIC·realm="FeedBurner·feed·ChucksTechWorld"(CR)(LF)
The "HTTP Viewer" service does non back upward feed authentication (and solely plant amongst "HTTP:" protocol). And, nosotros come across the result.
It's possible that this characteristic volition travel useful, amongst feeds that are used exterior Blogger (noting the Reading List ability). If you're publishing a Blogger blog, however, you're non probable to larn whatsoever useful result.
Owners of #Blogger blogs, which role the FeedBurner "Password Protector" service, may notice that the service delivers less protection - together with to a greater extent than or less interference - other than the service mention suggests. It would likely travel best to avoid role of this service.