How to Automatically Install and Enable a Chrome Extension

calendarAugust 6, 2021 in Chrome , Edge , HttpWatch

The HttpWatch installer adds the HttpWatch extension to Chrome but the user needs to manually approve it before its first use:

Our larger customers typically install HttpWatch through automated scripts using command line flags to silently run the installer. Unfortunately, the manual step shown above is still required on each PC before the user can access HttpWatch.

There is a way to force the installation of HttpWatch or any other Chrome extension using Chrome extension policies. The ExtensionInstallForcelist value specifies which extensions should be automatically installed and enabled from the Chrome Web Store. This value is stored in the registry in the following location for all users:


or in this location for a single user:


Each extension to be installed in this way must have a numbered value. For example, with HttpWatch the entry would be:

[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\ExtensionInstallForcelist] = "1"="dajhhgiioackgdldomhppobgjbinhimh"

In RegEdit it would look like this:

The next time Chrome restarts it will automatically download and enable the extension without requiring any manual intervention. An added advantage of doing this with HttpWatch is that no debugging banner is displayed in Chrome when HttpWatch is recording.

Microsoft Edge has a similar set of policies that can also be used to force the installation of an extension.

A New Way to Ask Questions and Make Suggestions About HttpWatch

calendarMay 20, 2021 in Uncategorized

As well as the usual ways of getting support we have recently added a Discourse forum for asking questions or sharing what you have done with HttpWatch.

There’s also a ‘Feature Request‘ category where you can suggest new ideas and vote on existing ones.

What’s New in Version 13.1?

calendarJanuary 8, 2021 in HTTP , HTTP/2 , HTTPS , HttpWatch

HttpWatch 13.1 is now available for download and includes the following new features.

Improved Display of URLs

The page URL (including fragments) is now shown for each page group making it easier to debug Progressive Web Apps (PWAs) where URL fragments may be used for navigation. Also by default, URLs are displayed relative to the containing page and the HTTPS scheme prefix is hidden:

Insecure HTTP Warning Symbol

A red warning triangle is displayed next to insecure HTTP requests:

URL Display Options

A new URL Display options tab can be used to configure how URLs are displayed:

Warning Generated When HTTP/2 Not Used

A new warning (HW1011) highlights requests that did not use HTTP/2 (or a later network protocol) and therefore may not have optimal performance:

Ready to get started? TRY FOR FREE Buy Now