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:
A red warning triangle is displayed next to insecure HTTP requests:
A new URL Display options tab can be used to configure how URLs are displayed:
A new warning (HW1011) highlights requests that did not use HTTP/2 (or a later network protocol) and therefore may not have optimal performance:
HttpWatch now supports Microsoft Edge version 80 or later using an extension hosted in the Microsoft Store:
You can now choose which browsers to use with HttpWatch when you run the installer. It is also possible to just install HttpWatch Studio if you just want to open existing HAR or HWL log files:
Automation scripts can use the HttpWatch automation interface to control HttpWatch in Microsoft Edge:
The Find Method can be used to quickly locate requests by URL or ID either within a page or a whole log file:
HttpWatch now restores extension and log windows to their original position even if they were placed with the Windows snap feature:
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:
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:
The cookie panel now displays the SameSite attribute for cookies received from the server:
The Result column in Chrome and Edge now shows whether the memory or prefetch cache was used:
HttpWatch now formats and applies password masking to JSON content even if the content type has been incorrectly set to a different format: