Add diagnostic headers to Akamai'd websites

Latest Version

Version
1.1
Update
February 19, 2015
Size
4.85KiB
Developer
Category
Users
10,000+
Rating
3.79167 ★
Manifest Version
2
Web Store Status
Languages Support
English
See more
Permissions
WebRequest
WebRequestBlocking

See more

Akamai debug headers Extension

Akamai debug headers makes it much easier to figure out what's happening with websites fronted by Akamai.

This simple, lightweight extension adds Akamai debug HTTP headers to your HTTP(S) requests, providing extra information like cache hits/misses, TTLs and cache keys.

to see it in action, download it now and test it out on reddit.com, dailymail.co.uk or xbox.com
Read more

Source Manifest.json

{"update_url": "https://clients2.google.com/service/update2/crx", "name": "Akamai debug headers", "version": "1.1", "description": "Add diagnostic headers to Akamai'd websites", "permissions": ["webRequest", "webRequestBlocking", ""], "background": { "scripts": ["background.js"] }, "manifest_version": 2}
Read more

How to download and manually install Akamai debug headers extension for Chrome

Looking for a way to install Akamai debug headers extensions for Chrome, you can search for them in the Chrome Web Store, clicking the "Add to Chrome" button, and following the straightforward process.

However, you may need to install Akamai debug headers extensions manually, this article outlines two simple methods to effortlessly install Akamai debug headers extensions, whether they come as unpacked folders in compressed formats like .zip or as .crx files.

Method 1: Download Akamai debug headers extension and manually install through Drag &Drop

If you ever need to manually install a Akamai debug headers extension for Chrome, don't worry, it's a simple process. Just follow these easy steps, and you will have your extension ready to use in no time.

Step 1: Download the Akamai debug headers Extension by clicking the "Download CRX" button on the website.

Look for the Akamai debug headers extension you wish to install. Go to the website and download the Akamai debug headers extension package, which is usually a .CRX file and comes in a zipped file. Here ".crx" file is the format for Akamai debug headers extension that contains all the data.

Step 2: Extract &Arrange Files

Once the file is downloaded, extract that file into its own folder. Similarly, give that extension files a permanent home. In other words, keep it in a folder that you don't accidentally delete it because these files will be needed to make that extension work.

Step 3: Go to the Chrome Extensions Page

Open Google Chrome and in the address bar, type chrome://extensions; it will open the Google Chrome extensions page. Make sure that "My extensions" is selected in the sidebar.

Step 4: Drag and Drop the Extension

Now, go to the folder where you extracted the Akamai debug headers extension and drag &drop the extension file from there anywhere onto the extension page within Google Chrome.

Step 5: Complete the Installation

Once you drag and drop the extension file, follow the steps that Google Chrome takes you through. Similarly, if the extension file is of .crx file format, you will be required to review the permissions and then add the extension.

Now, you can manage that added extension as you would like to with any other Chrome extension that you added through Chrome Webstore. Its icon will also appear in the Google Chrome Menu on the right side of the address bar once you activate it.

Method 2: Download Akamai debug headers extension for Chrome and install in Developer Mode

This is another method to install Akamai debug headers extension manually, but the twist is that here, you install by enabling the developer mode option provided in Google Chrome. This mode is commonly used for testing extensions or running unpublished tools.

Step 1: Download the Akamai debug headers extension file

Select and download the Akamai debug headers extension by clicking the 'Download CRX' button on the website.

Step 2: Extract the downloaded contents

Convert the file to a ZIP file if it is in CRX format then extract the Akamai debug headers extension zip file or folder that you downloaded. Make sure you extract it using the same folder name and keep it safely in another folder, so you don't delete it by mistake. The extracted folder will be needed to keep your Akamai debug headers extension running.

Step 3: Open Chrome Extension Setting Page

In the address bar of Google Chrome, type chrome://extensions and open the Chrome Extension Page.

Step 4: Enable Developer Mode

After opening the Chrome Extension page, look at the top right side, and you will find the toggle option of "Developer mode."Simply enable that developer mode option.

Step 5: Load the Unpacked Extension

Once you enable the developer mode option, you will see the menu of Load Unpacked, Pack Extensions and Update. From that, select the option "Load unpacked."

Step 6: Select the Extension Folder

Once the pop-up opens upon clicking Load unpacked, select the Akamai debug headers extension directory and click on the "Select Folder "button.

Step 7: Confirm and Install

After you select an extension folder of a Google Chrome extension you're installing manually, confirm its installation for the final time and let the installation complete.

Conclusion

Here we've made a step-by-step guide on How to manually install Akamai debug headers extension in 2 ways. We hope this guide proves helpful.

Similar Extensions

icon

Akamai Developer Toolkit Extension · Developer Tools 10,000+ 7 ★ 10.34MiB

icon

Pragma Header Extension · Developer Tools 10,000+ 0 ★ 167KiB

icon

CDN Headers & Cookies Extension · Developer Tools 10,000+ 63 ★ 284KiB

icon

JSONVue Extension · Developer Tools 10,000+ 2651 ★ 181KiB

icon

Piez Extension · Developer Tools 10,000+ 17 ★ 266KiB

icon

Modify Header Value (HTTP Headers) Extension · Developer Tools 10,000+ 46 ★ 94.33KiB

icon

ModHeader - Modify HTTP headers Extension · Developer Tools 10,000+ 1061 ★ 676KiB

icon

Akamai Cache Eraser Extension · Developer Tools 10,000+ 8 ★ 25.71KiB

icon

Requestly - Intercept, Modify & Mock HTTP Requests Extension · Developer Tools 10,000+ 1227 ★ 876KiB

icon

Omnibug Extension · Developer Tools 10,000+ 50 ★ 1.35MiB

icon

Adobe Experience Platform Debugger Extension · Developer Tools 10,000+ 27 ★ 1.99MiB

icon

Debugger for Adobe Analytics Extension · Productivity 10,000+ 56 ★ 17.19KiB

icon

Tealium Tools Extension · Productivity 10,000+ 28 ★ 2.13MiB

icon

Launch and DTM Switch Extension · Developer Tools 10,000+ 192 ★ 215KiB

icon

Web Vitals Extension · Developer Tools 10,000+ 43 ★ 398KiB

icon

AEM Chrome Plug-in Extension · Developer Tools 10,000+ 17 ★ 222KiB

icon

Page load time Extension · Developer Tools 10,000+ 256 ★ 19.72KiB

icon

ObservePoint Debugger Extension · Developer Tools 10,000+ 52 ★ 3.6MiB

icon

AMP Validator Extension · Developer Tools 10,000+ 97 ★ 2.51MiB

icon

Google Analytics Debugger Extension · Developer Tools 10,000+ 533 ★ 28.88KiB

icon

dataslayer Extension · Developer Tools 10,000+ 80 ★ 417KiB

icon

Performance-Analyser Extension · Developer Tools 10,000+ 43 ★ 26.12KiB

icon

Adobe Target VEC Helper Extension · Developer Tools 10,000+ 13 ★ 546KiB

icon

axe DevTools - Web Accessibility Testing Extension · Accessibility 10,000+ 114 ★ 2.89MiB

User reviews

icon

Niklas H (ID: 0000008375edd7dc) Voted 1 ★ - Updated 11/01/2021 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...

icon

Juan Luis Baptiste (ID: 000000ce61454403) Voted 1 ★ - Updated 09/04/2020 It is not working, no additional headers appear when looking at a request from a site being on Akamai.

icon

Jesse (ID: 000000b4df9afcbc) Voted 1 ★ - Updated 08/03/2019 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

icon

Eddie Yee (ID: 00000025c1201b24) Voted 1 ★ - Updated 04/01/2019 Useful but needs to get fixed. The extension definitely still causes ERR_SPDY_PROTOCOL_ERROR errors on many sites that use the SPDY protocol.

icon

Kiran Edem (ID: 000000a4fffd444c) Voted 1 ★ - Updated 10/17/2018 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.