ldelossa

# GCE vimeo-logs shortcuts
# Images shortcuts
logs-lim() { gcloud --project vimeo-logs compute images list }

logs-rmim() { if [ $# -eq 0 ]; then echo "Deletes an image: [image-name]"; else
            gcloud --project vimeo-logs compute images delete $1; fi }

# Instances shortcuts
logs-li() { gcloud --project vimeo-logs compute instances list }

ldelossa

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. 

ldelossa

config = """global
    log 127.0.0.1 local1 notice
    chroot /var/lib/haproxy
    user haproxy
    group haproxy
    daemon
    stats socket /var/run/haproxysock level admin

defaults
    log global