From August 26th, 2014 to November 1st, 2021, 44% user give 5-star rating, 6% user give 4-star rating, 13% user give 3-star rating, 38% user give 1-star rating. for Akamai debug headers chrome extension.
This extension does the job (extends DevTools Network-tab with akamai-header information) however it's extremely dangerous because once it's activated it will break many requests. For example sites like Favro and Zeplin become unusable. It also destroys some resource requests on my own site. Worst of all is that even if you just use the extension once during a test, then disable it, it tends to magically re-activates itself months later (perhaps when you update Chrome?). We've found that all of a sudden someone in the team sends an alarm about resource requests not working on my site. But it just turns out that they've got this Akamai extension installed and it's magically activated itself without them knowing. Really scary and error-prone extension. It does the job but you basically have to make sure you uninstall it after every time you use it - it's risky leaving it installed and will lead to many herrings as you report suspected errors on various sites, which are just caused by the extension...
It is not working, no additional headers appear when looking at a request from a site being on Akamai.
Causing ERR_SPDY_PROTOCOL_ERROR errors on a ton of sites. Also since Chrome 76, this extension is causing the following error: Access to XMLHttpRequest at '...' from origin '...' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status. Hopefully this gets fixed
Useful but needs to get fixed. The extension definitely still causes ERR_SPDY_PROTOCOL_ERROR errors on many sites that use the SPDY protocol.
This plugin is causing sites like Adobe.com and expedia.com to not to load. The moment I add this plugin, I am seeng ERR_SPDY and 502 errors on few websites.
NOTE: This extension may cause intermittent ERR_SPDY_PROTOCOL_ERROR errors in Chrome. The Akamai Engineering team are working on resolving this issue, but in the mean time, the following Solution / Workaround can be used. Solution: Remove the "akamai-x-get-extracted-values" Akamai Pragma header from the HTTP request header when accessing the site
Was great, but on some Akamai routes it's resulting in ERR_SPDY_PROTOCOL_ERROR
Doesn't appear to work on newer releases.
It would be nice if it had a way of enabling/disabling it easily from the button in the top bar. I don't want to send the Pragma header for all sites, so I have to manually enable/disable the plugin.
very good
good
Excellent tool. Loved it. Good job developers.
Great plug-in for debugging akamai header values and caching rules. Excellent.
Awesome extension.
It just works. Easy as pie.
Excellent product for debugging Akamai caching.