Secure Feeds for a Secure Web

Our website and all feeds originating from our gateway are now SSL encrypted and delivered over HTTPS. It will make client-server communication more secure, and also improve content reach with a higher placement now that Google considers HTTPS as a ranking signal.

All Corporate accounts (hosted separately) are now HTTPS as well, except for those that have the domain alias feature activated, making their feeds mask under their own domain or sub-domain name (e.g. http://feeds.yourdomain.com).

We realize that not all external systems and services are SSL compatible yet, and hence they can’t accept HTTPS feeds. Ironically, and disappointingly, Google FeedBurner is one such major service. So, for now we have enabled both HTTP and HTTPS (by default) for all feeds. You can choose which one to use depending on the consumer capability.

Advertisements

One Comment on “Secure Feeds for a Secure Web”

  1. julien51 says:

    Great move!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s