History

The History tab lists the requests your endpoint received, newest first. Select one to inspect it. The list refreshes on its own while Auto-refresh is on.

What is recorded

• The request: time, method, path and query, headers and body.
• The forwarded URL, when the request was forwarded.
• The request body after the request template ran, with the template's name, or the error if it failed.
• The target's answer: status, headers and body, when the request was forwarded. Headers the proxy does not relay, like Set-Cookie, are shown here too.
• How long the request took, and the error, if Middleman turned the request away or the forward failed.

Cookies Middleman sets for the dashboard and the headers added by its hosting are never recorded. See what Middleman changes.

How long it is kept

An endpoint keeps its latest 100 requests, and none older than 7 days. Whichever limit is reached first applies. Older requests are deleted.

To remove a request sooner, delete it with the × on its row. To remove several, tick them (or Select all) and press Delete selected.

Large bodies

Each body is stored up to 64 KiB. A longer body is cut off and marked truncated in the inspector. Forwarding is not affected: the target gets the whole body, up to the 1 MiB request limit.

Hiding header values

List header names in the Config tab, under Redacted headers, separated by commas, for example Authorization, Cookie, X-Api-Key. Names are not case sensitive.

• History then stores [redacted] in place of each listed header's value. The name stays, so you can still see the header was sent.
• Only History is affected. Your target still receives the real values.
• It applies to request headers, and to requests received after you save. Requests already recorded keep their values until they expire or you delete them.
• A redacted value is gone for good. It cannot be recovered from History, which matters if you plan to resend a request.
• Nothing is redacted by default.