To debug Akamai-cached content you simply need to send properly formed Pragma
header.
curl -H "Pragma: akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-check-cacheable, akamai-x-get-cache-key, akamai-x-get-extracted-values, akamai-x-get-nonces, akamai-x-get-ssl-client-session-id, akamai-x-get-true-cache-key, akamai-x-serial-no" -IXGET http://www.fifa.com/
curl -H "Pragma: akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-check-cacheable, akamai-x-get-cache-key, akamai-x-get-extracted-values, akamai-x-get-nonces, akamai-x-get-ssl-client-session-id, akamai-x-get-true-cache-key, akamai-x-serial-no" -H "Host: www.fifa.com" -IXGET http://wildcard.fifa.com.edgesuite-staging.net/
Note Host
header.
Example: X-Check-Cacheable: YES
Informs whether resource is cacheable by Akamai.
Example: TCP_MEM_HIT from a80-239-171-156 (AkamaiGHost/6.9.4-9930199)
a80-239-171-156
is Akamai server that returned output (80.239.171.156).
If-Modified-Since
request.IF-Modified-Since
request.IF-Modified-Since
request from client and object was fresh in cache and served.Example: X-Cache-Key: /L/1758/81636/2m/www.fifa.com/
81636
is a CP code, 2m
is cache TTL at Akamai side (it may be different when set at application level through Edge-Control
header).