Deliver Feeds to FeedBurner From SSL Enabled Website via Cloud Files

Yes, we can easily use Cloud Files to deliver feeds to FeedBurner from SSL enabled websites to avoid error related with HTTPS feed and FeedBurner. SSL enabled websites is actually not the right terminology, it should be TLS enabled. With the word “Websites” we are practically meaning WordPress websites. It can be difficult to pass only one URL via non HTTPS or over Port 80, if we use certain Plugins. Practically, to avoid bias of subscribing to Website’s feed, the FeedBurner Redirection feature is used. But, adding a non-HTTPS URL might break the security browser pad lock in certain device and browser combination. This method has this minute flaw.

 

Deliver Feeds to FeedBurner From SSL Enabled Website via Cloud Files : Basics

 

Basics of how to use Cloud Files to deliver feeds to FeedBurner from SSL enabled websites to avoid error related with HTTPS feed and FeedBurner actually adapted from our own solution described before – WordPress HTTPS and Feedburner – Easy Solution. You should read it as we will not repeat the same basic principle.

 

Deliver Feeds to FeedBurner From SSL Enabled Website via Cloud Files : Steps

 

If you already have / using Rackspace Cloud, you practically might be using Rackspace Cloud Files. If you are not an user, you need to have a Rackspace Cloud Account. Charge is very less, it will be hardly few cents per month for Rackspace Cloud Files part only. This is a good alternative way if you do not have a shared hosting account or a spare domain. If you want to decorate more, you can set CNAME for Feed only Container.

So, the steps are pretty easy :

 

1. Get Feed’s source code from WordPress default URL ( with Pretty Permalink ON ); like from http:// thecustomizewindows.com/feed/ in our case. It is just a browser feature which need not be used.
2. Copy and Save the Content as feed.xml
3. Create a Container, probably better with a name like feed-domain-name or simply feed
4. Upload the file.
5. Grab the URL (non SSL)
6. Change the feed source in FeedBuner with the CDN’s full URI.
7. Technically you should manually delete and upload newly generated xml file every time you publish posts.

 

As there are lot of tools for OpenStack Swift like Swiftly and hundreds of developer resources, it can be automated. You can use API based simple script for automation. For full managed Account, you might personally ask any Racker for making this uploading part easier. There are enough great peoples to think or develop a script for you, although it might not be their work. You can use Cyberduck to avoid account login for manual update. Manual Update is better as it will be very faster.

Funnily, it makes Feedburner to update Feed more faster, probably as it is CDN ! You can not ping, that is a problem.

This Article Has Been Shared 955 Times!

Facebook Twitter Pinterest