Responses
Press ⌘↵ or Send. The bar above the response shows the status, the time and the size.
Body
JSON is shown Pretty: re-indented without changing a single value, so large numbers and the order of keys stay exactly as the server sent them. Raw shows the body as it came. Fold objects and arrays with the arrows next to line numbers; ⌘F searches the body.
Images are shown as images. Any body can be copied or saved to a file.
A very large response is shown without syntax highlighting, so the window stays fast.
Headers
The Headers tab lists the response headers as they came.
Cookies
The Cookies tab lists the cookies the server set with this response and says what went into the cookie jar. Manage cookies… opens all the cookies FleetFoot keeps. See Cookies.
Timeline
Hover the time to see where it went. The Timeline tab shows the same phases with the connection log:
| Phase | What happens |
|---|---|
| DNS lookup | finding the server’s address |
| TCP connect | opening the connection |
| TLS handshake | setting up HTTPS |
| Waiting (TTFB) | the server works on the answer |
| Download | the response comes in |
The connection log shows the request exactly as it went out (lines with >), the response headers (<) and notes about the connection and TLS (*). Every request opens a new connection, so the phases are always complete.
Errors
When a request fails, FleetFoot says why — the host is not found, the connection is refused, a certificate is not trusted, time ran out — with what to check. For a self-signed certificate, turn off Verify TLS certificate in the request’s Settings tab or in the app settings.