HttpWatch

HttpWatch records, inspects and shares Chrome/Edge network traffic for developers, QA and support teams. From the team that co-designed the HAR spec

[HttpWatch @HttpWatch]

(4/4) Deploying across an organisation? Run Setup with /all-users=1 from an elevated process for an All Users install, silent or interactive.

[HttpWatch @HttpWatch]

HttpWatch 16.1 is out. This release is all about making HttpWatch trivial to install — starting with not needing admin rights. 🧵(1/4)

[HttpWatch @HttpWatch]

(3/4) Upgrading from 16.0 or earlier?

Those versions always installed for all users, so Setup asks whether to stay All Users or move to This User. Either choice needs admin rights, because the old all-users setup has to be updated or removed.

[HttpWatch @HttpWatch]

https://t.co/POlmPDG6xM

[HttpWatch @HttpWatch]

Customer says they can’t stay logged in.

Server logs look fine. The login response returns 200 OK. The Set-Cookie header is there.

But the browser may still reject the cookie because of SameSite, Secure, domain or path rules — or the cookie may be overwritten by JavaScript.

With HttpWatch Basic, you can ask the customer to record the problem for free on a Windows PC and send you the saved HWL log file.

Open it in HttpWatch Professional to see the cookies sent with each request, cookies returned by the server, browser cookie warnings, and where cookies were assigned in JavaScript.

[HttpWatch @HttpWatch]

New in HttpWatch v16: improved console capture for Chrome and Edge.

Recorded traces can include console errors, warnings, info messages, JavaScript runtime errors, timestamps, page details and stack frames where available.

When a customer sends you an HttpWatch HWL file, that console output is preserved alongside the network trace, so you can review it later in HttpWatch Professional.

By contrast, a HAR file saved from browser DevTools only captures network traffic, not the console output that may explain why the request failed.

[HttpWatch @HttpWatch]

For hard-to-reproduce browser issues, the goal is simple:

Capture what actually happened on the customer’s machine, save it, and share it with the people who can diagnose it.

That is where a detailed HttpWatch trace can make support cases much easier to resolve.

Find out more at https://t.co/XAH1M0tT6M
(8/8)

[HttpWatch @HttpWatch]

Debugging a customer-only web issue?

The failed request is only part of the story. Console errors, blocked cookies, cache behaviour, redirects, timings, headers and browser details often explain why the issue only happens for one user.

That surrounding context is what makes a trace useful.
(1/8)

[HttpWatch @HttpWatch]

The support team can open the customer’s HWL file in HttpWatch Professional.

That gives them the detailed diagnostic information needed to investigate the issue: headers, timings, cookies, redirects, cache details, console messages and browser environment.

Much better than trying to debug from screenshots alone.
(7/8)

[HttpWatch @HttpWatch]

HttpWatch 16 is here 🚀

Track cookies set by JavaScript, analyze richer console output, spot incorrect content types, and get better Chrome/Edge integration — all designed to make browser network debugging faster and clearer.

Download the latest version:
https://t.co/PbZv0XiguQ

[HttpWatch @HttpWatch]

HttpWatch featured in 'Trending extensions on Microsoft Edge Add-ons'

https://t.co/wEXQPxRcwD

[Microsoft Edge Dev @MSEdgeDev]

Looking for productivity help on Microsoft Edge? Check out these trending #EdgeExtensions:

@Outlook
@Dynatrace
@ModernKitOne Flash Player 2021
@HttpWatch
ImageAssistant Batch Image Downloader
Video Downloader-CocoCut https://t.co/oXBiLnN4YO

[HttpWatch @HttpWatch]

Blog Post : How to Automatically Install and Enable a Chrome Extension - https://t.co/3abu0G5fWe

[HttpWatch @HttpWatch]

Got a feature request, suggestion or question about HttpWatch? Or perhaps you'd like to share something you've done with HttpWatch?
Please try our new Discourse forum - https://t.co/ALiFjQtLH6