Skip to content

Instantly share code, notes, and snippets.

@ldelossa
Created August 15, 2017 03:31
Show Gist options
  • Save ldelossa/767ab032440bcaf45af983e7f9666183 to your computer and use it in GitHub Desktop.
Save ldelossa/767ab032440bcaf45af983e7f9666183 to your computer and use it in GitHub Desktop.
Akamai does not serve an asset retrieval when client is in specific geographic regions.
Summing up this github issue:
https://github.com/videojs/videojs-contrib-hls/issues/1232
If a client makes a request to player.vimeo.com a Geo-Country-Code http header is tagged onto this request. When the request with this Geo-Country-Code header gets to the player server it will evluate this and determine which CDN to return. We are experiencing an issue where a request for the same asset made from US (physical location) succeeds but made from a client in Latam fails.
A follow-up message informs us that removing the crossOrigin attribute from the video tag allows it to work. They go on to say that headers are not correct on the responses.
I do not have a method of attempting a true (physical) lookup from another physical\geo location.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment