Guessing the FW is a new addon, since the links was always just from downloading from v.giantbomb.com (guessing that was a cname for akamai), and that worked fine.
My concern was not by adding my API key over http, eventhough it does not change that people can obtain this and use it to dl videos as if they were me (at least it is not my username and password). The old description of how to get the premium feed to work with a podcast player was to add your username and password (as basic auth) to the url, e.g. http://markuskrogh:firstname.lastname@example.org/podcast (can't remember if it was part of the welcome mail or where I read it, but I remember i dropped it because of that)
Well you do listen on 443, and you do have a valid certificate, since you redirect from https to http. (subject: C=US; ST=California; L=San Francisco; O=CBS Interactive Inc.; CN=*.giantbomb.com)
PS. the editor is not fun to add an @, since it hijacks with the "who do you want to mention".
Why on earth can't you add the API key to the download links, such that it will work with wget without me having to jump through hoops and loops. You could always add it as a download key if you do not wan't to add an API key for people who do not have it.
It is kind of why I never used the premium podcast feed, as I needed to add my credentials to a non https url.
Also why do you redirect from https to unencrypted http, that makes about 0% sense?