@laika: If you open the Giant Bomb add-on and hit "C", you should get a menu that includes "Add-on settings" at the bottom. Hit that, and it'll show a dialog with a quality selector. "Auto" means "try to get HD if the API returns an hd_url". You can verify that you're getting an HD video by hitting "I" (the letter eye) and checking if the path for the video starts with "http://www.giantbomb.com/api/protected_video/".
I can access subscriber content without issues if I set the quality to "High" (I tested with the May 23 Unprofessional Friday).
But that's not the important part. The important part is that I figured out what's happening. I finally decided to just open up Wireshark and watch the HTTP traffic. The request from XBMC for the HD video link (http://www.giantbomb.com/api/protected_video/2300-8925/?download=1&api_key=<MY_API_KEY>) gets a 403 Forbidden response. I narrowed it down to the User-Agent string that my version of XBMC supplies. After deleting bits of it until I found the smallest substring that still fails, I got "a6". It seems that A6 is a web spider for some ad platform or something. I'm guessing whatever the protected_video URLs go through is trying to ban that spider, but the ban is a little broader than it ought to be.
There are, I suppose, two solutions: either make the User-Agent ban a bit more specific, or have the Giant Bomb add-on specify a custom User-Agent. You can do this by appending the string "|User-Agent=Whatever" to URL for the video. XBMC will parse that out and use "Whatever" as the User-Agent when making the HTTP request.
EDIT: Oh, and the "a6" in my User-Agent comes from the Git commit ID for the version of XBMC I'm on.
Log in to comment