Good news! Giant Bomb is going SSL! But what does that mean for you?
We're enabling SSL as an option for all requests to the site and we will be delivering all our assets linked in our articles and API calls with SSL.
So, for example the URLs in the API responses for images and video will change from:
Images changing from http://static.giantbomb.com to https://static.giantbomb.com
Progressive video (MP4) changing from http://v.giantbomb.com to https://giantbomb-pdl.akamaized.net
Streaming video (M3U8) changing from http://hdv.giantbomb.com to https://giantbomb-vh.akamaihd.net
This shouldn't require any work from you unless you are for some reason manipulating the URLs before requesting them or hard coding the URL protocol, so make sure you're not doing that!
Our timeline for going live with this is the week of March 6th. We plan on forcing SSL for the site as a whole after this change has been up and running for a while. Once that is in place your app should be hitting the SSL URL directly or be able to handle the SSL redirect that we will do automatically
So, in summary:
- For API applications that explicitly use links in API XML/JSON results, there should be no changes to your app needed since the links will become SSL when this change goes live. If you do have any hard coded hostnames for video or images though, you will need to pay attention to the changes being made.
- The old non-SSL URLs will continue to work for a short time even after this change goes live. But we highly recommend you make any changes needed as soon as possible. Again, as long as you have no hard coded URLs or hostnames, and are simply using the links provided in API results, no changes will be needed.
If you have any questions feel free to ask below!
Log in to comment