Debugging Akamai

To debug Akamai-cached content you simply need to send properly formed Pragma header.

Production example

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/

Staging example

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.

Response headers

X-Check-Cacheable

Example: X-Check-Cacheable: YES

Informs whether resource is cacheable by Akamai.

X-Cache

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).

X-Cache-Key

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).

  1. by sobstel • November 2012 • blog archive