Akamai debug headers
Add diagnostic headers to Akamai'd websites
Total ratings
3.79
(Rating count:
24)Review summary
These summaries are automatically generated weekly using AI based on recent user reviews.
Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate,
spammy, or outdated. Pros
- Works perfectly to view cache hit/miss for individual requests.
- Extends DevTools Network-tab with Akamai header information.
- Useful for debugging Akamai header values and caching rules.
- Received positive feedback for functionality when it works.
Cons
- Can break many requests leading to unusable sites.
- Tends to reactivate itself unexpectedly after being disabled.
- Causes ERR_SPDY_PROTOCOL_ERROR and CORS policy issues.
- Requires manual enabling/disabling, which can be cumbersome.
Most mentioned
- Causes ERR_SPDY_PROTOCOL_ERROR errors.
- Reactivates itself without user knowledge.
- Breaks functionality of various sites.
- Requires uninstallation after use to avoid issues.
Upgrade to see all 35 reviews
User reviews
Recent rating average:
1.40
All time rating average:
3.79
Upgrade to see all 35 reviews
Rating filters
5 star 4 star
3 star
2 star
1 star
| Date | Author | Rating | Lang | Comment |
|---|---|---|---|---|
| 2024-02-26 |  | | en | I manage many sites fronted by Akamai, and it works perfectly to view the cache hit/miss for individual requests. Much easier than running cURL each time. |
| 2021-11-01 |  | | 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... | |
| 2021-11-01 |  | | en | 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... |
| 2020-09-04 |  | | It is not working, no additional headers appear when looking at a request from a site being on Akamai. | |
| 2020-09-04 |  | | en | It is not working, no additional headers appear when looking at a request from a site being on Akamai. |
| 2019-08-02 |  | | 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 | |
| 2019-08-03 |  | | en | 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 |
| 2019-04-01 | Eddie Yee | | Useful but needs to get fixed. The extension definitely still causes ERR_SPDY_PROTOCOL_ERROR errors on many sites that use the SPDY protocol. | |
| 2019-04-01 |  | | en | Useful but needs to get fixed. The extension definitely still causes ERR_SPDY_PROTOCOL_ERROR errors on many sites that use the SPDY protocol. |
| 2018-10-17 |  | | 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. |
Upgrade to see all 35 reviews