What is the best way to eliminate Akamai headlines these days?

Traditionally, I checked Akamai headers by installing a Firefox extension called akamaiheaders.xpi . Unfortunately, I think the latest version of Firefox to support this was 3.

As I understand it, this plugin will add special headers to all the HTTP requests that Firefox made, which prompted Akamai to add a bunch of headers to the response (telling if the file was cached, where it got it from, etc.). Then, using a tool like HTTPFox or Firebug, I could easily see which assets were cached and which were not.

I searched everything, but I cannot find anything so simple and easy to use. Does anyone know anything that allows me to keep track of all the Akamai headers for all the resources that my browser loads that work in either FF, Chrome, or Safari?

+8
browser header akamai
source share
7 answers

If you can find the akamaiheader.xpi file, you can simply open it and change maxVersion in install.rdf to 9 ..

.xpi files are just ZIP files, and on most machines you can simply add .zip to the file name and double-click on it.

+1
source share

You can use curl and / or wget for this:

 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.oxfordpress.com/ 

or

 wget -S -O /dev/null --header="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" http://www.oxfordpress.com/ 

If you want to test the staging environment, you need to remember to send the Host header, for example:

 curl -H "Host: www.oxfordpress.com" -H "Pragma: ..." -IXGET http://oxfordpress.com.edgesuite-staging.net/ 

One way or another, it always sends the correct Pragma headers and then reads the response headers.

A list of Pragma headers as well as explanations for the X-Cache response header can be found here: http://webspherehelp.blogspot.com/2009/07/understanding-akamai-headers-to-debug.html .

+17
source share

I know this question is old, but since I found it in my search today, I thought I would add an answer for the next person who comes.

There are several extensions in the Chrome Store:

Akamai's debugging headers is the one I chose, and it has been working well so far.

+8
source share

You can use a local proxy server (for example, Fiddler or Charles Proxy , my personal favorite) and add the following header to outgoing requests:

Pragma: akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-check-cacheable, akamai-x-get-cache-key, akamai-x-get-extract-values, akamai- x-get-nonces, akamai-x-get-ssl-client-session-id, akamai-x-get-true-cache-key, akamai-x-serial-no

+6
source share

If you use Chrome or Chromium, you can use the Header Hacker or Pragma Header extensions. With one of them you will have to add Pragmas manually.

+4
source share

To debug akamai headers, for the Chrome browser try this extension: CDN headers and cookies - Chrome Web Store https://chrome.google.com/webstore/detail/cdn-headers-cookies/obldlamadkihjlkdjblncejeblbogmnb

Note. Turn on “Download Akamai Headers” in the settings (click on the “Lego minifig Head” icon, click the gear and check the box “Download Akamai Headers”).

It has been proposed in the Akamai community. https://community.akamai.com/community/web-performance/blog/2015/03/31/using-akamai-pragma-headers-to-investigate-or-troubleshoot-akamai-content-delivery

+1
source share

They have a new version of XPI that you can download from Luna. There is also another plugin that adds a “content source” panel to Firebug to quickly link to what was on the page Akamaised.

As I said, to download both plugins you need to log into Luna and look in the "Support"> "Advanced Tools"> "Browser Extensions" section. XPI is not publicly available.

YMMV, but as far as I remember from colleagues, the Exceda plugin duplicated HTTP requests, which can be a little dirty during debugging.

For Chrome, I find ModHeader + Profile Settings, which sends Pragma headers.

0
source share

All Articles