← All features

Debugging

See what really happened

When a response isn't what you expected, Reqjet shows more than the body: where the time went, the TLS connection and certificate, any tokens involved, cookies, redirects and CORS.

Timing splits a request into DNS, connect, TLS, waiting for the server, and download.

Connection

TLS and certificate details

The HTTP and TLS versions, the cipher, the server's certificate (names, issuer and valid dates, with a warning when it expires within a month) and how much compression saved.

TLS 1.2, the certificate and its dates, and a body 37% smaller on the wire.

Tokens

JWTs decoded on the spot

Any JWT the request sent or the response returned is decoded: its header, its claims with readable dates, and whether it has expired. A 401 sent with an expired token says so.

The token sent in the Authorization header, decoded (not verified).

Cookies explained

Each cookie the response set, with its flags, and whether it was stored, deleted or rejected, and why. Cookies set on a redirect are followed as a browser would.

Check CORS

Checks a request as a browser on another origin would: whether a preflight is needed, what it's answered, and which headers a page can read.

Save as HAR

Write the requests and responses as a HAR file for a bug report or browser dev tools, with credentials hidden unless you choose otherwise.

Reqjet logo

Try it on your own requests

Free for Windows, macOS and Linux, and it opens the .http files you already have.