With FeedBurner, is it a good idea to diagnose any problems experienced.
After a brief feed diagnostic procedure, we do an HTTP trace of the feed.
Sending request:OK, the feed is redirected to FeedBurner.
GET /feeds/posts/default HTTP/1.1
Host: myblog.blogspot.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.19.191
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·302·Moved·Temporarily(CR)(LF)
Content-Type:·text/html;·charset=UTF-8(CR)(LF)
X-Frame-Options:·ALLOWALL(CR)(LF)
Location:·http://feeds.feedburner.com/MyCustomFeed(CR)(LF)
Given a problem involving FeedBurner, it is a good idea to use the FeedBurner "Troubleshootize" wizard.
All feed problems won't involve FeedBurner - and all FeedBurner problems won't affect only the blog subscription options - but a careful diagnostic procedure is still a good idea.
0 comments:
Post a Comment