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:
You can now choose which browsers to use with HttpWatch when you run the installer. It is also possible to only install HttpWatch Studio if you just want to open existing HAR or HWL log files:
URL Indicator Symbols Show the use of Fetch and XmlHttpRequest APIs
In Chrome and Edge an arrow symbol next to a URL shows that a request was created using the XmlHttpRequest (XHR) API in Javascript:
Or an arrow head symbol if the Fetch API was used:
Displays Service Worker Activity
When a service worker script intercepts a request the Result now displays (Service Worker). The status code is available in the data tip or Overview Tab:
A diamond URL indicator is used to show the outgoing requests made by a service worker:
Supports Snapped Window Positions
HttpWatch now restores extension and log windows to their original position even if they were placed with the Windows snap feature:
Displays SameSite Cookie Attribute
The cookie panel now displays the SameSite attribute for cookies received from the server:
Shows The Use of the Memory and Prefetch Cache
The Result column in Chrome and Edge now shows whether the memory or prefetch cache was used:
Detects The Use of JSON Without The Correct Content Type
HttpWatch now formats and applies password masking to JSON content even if the content type has been incorrectly set to a different format:
The latest update to HttpWatch includes experimental support for the beta version of Microsoft Edge (Chromium). Full support, including automation, will be added at a later date when Edge (Chromium) is officially released.
The Microsoft store does not yet support chromium based browser extensions but you can install the HttpWatch extension from the Chrome web store instead. The following steps guide you through adding HttpWatch to Edge Chromium
3. Allow Edge to Install HttpWatch from The Google Web Store
Open Edge (Chromium) Beta and go to …->Extensions or enter ‘edge://extensions/’ in the location bar. Then select ‘Allow extensions from other stores’ and click Allow:
4. Install the HttpWatch extension from the Chrome Web Store
Then click ‘Add To Chrome’ which will add the extension to Edge:
Once the extension has been added you can either access HttpWatch from the toolbar icon or by right clicking on the web page and selecting ‘Open HttpWatch’.
Blog
