New features: Canonical Headers and Pull HTTPS

Canonical Headers and Pull HTTPS

More Features, Such Waw!

Another week, another bunch of new features! Looking back at last week, we felt like we could have done more in terms of functionality. So we decided to ask you guys (yes you!) to give us some feedback to tell us what you want, and frankly we got more than we bargained for!

Condensing the list down to the essentials, we feel like the following new features are a step in the right direction to building something amazing to not only speed up your site, but give you guys the functionality you deserve.

Canonical Headers

Canonical Header

What is it?

Canonical headers tell the browser where assets originally came from, for instance if you have an image on your site that’s already been used on another page, the canonical header will point to it- This helps backtrack to an asset’s source and also helps search engines rank content.

How is it used?

Search engines hate content duplication, but by setting the canonical header live on your resource it helps define where your assets came from and ranks your content higher.

Pull HTTPS

Pull HTTPS

What is it?

When visiting a resource’s asset it pulls content over HTTPS, so for instance when entering into the URL bar “myresource.a.cdnify.com/image.jpg”, the image will be transferred using the HTTPS protocol.

How is it used?

If an asset is requested via HTTP you can force it to be delivered via HTTPS, securely delivering assets using SSL.

Features, Features, Features!

As if that wasn’t enough, we’ve added SPDY support which you can check out at: SPDY 3.1 – Also, you can now select custom date ranges for your stats.

Now’s the time to tell us what you think – Do you like the new features? What would you like to see built next?

Drop a message in the comments below or get in touch with us over at CDNify Contact.

Enjoyed this blog post?