Reading Responses

After you send a request, Vegha shows the result in the response viewer. It presents the status, timing, and size at a glance, with the full body, headers, and cookies available below.

Status line

The status line summarizes the outcome of the request:

Field	Meaning
Status	The HTTP status code and reason phrase
Time	Total elapsed time for the request
Size	The size of the response

The connection timeline

For HTTP requests, Vegha breaks the total time into the phases of the connection so you can see where time was spent:

Phase	What it measures
DNS	Resolving the hostname to an IP address
Connect	Establishing the TCP connection
TLS	Completing the TLS handshake
TTFB	Time to first byte — waiting for the server to start responding

This makes it easy to tell whether a slow request is slow because of DNS, connection setup, the TLS handshake, or the server itself.

Response body

The body is shown with formatting and syntax highlighting appropriate to its content. JSON and XML responses are formatted for readability. The viewer reflects the content type returned by the server.

Headers and cookies

The response viewer includes the full set of response headers and any cookies returned by the server. Cookies are also stored in Vegha’s cookie jar, so they are sent automatically on later requests to the same host — see HTTP & REST requests.

Saving responses

You can save a response to a file from the response viewer. This is useful for capturing a payload as a fixture, sharing an example with a teammate, or comparing results over time.

Tests

If the request defines tests, the results appear in the Test Results view alongside the response, showing which assertions passed and which failed. See Scripting for writing tests.

Tip

When a request feels slow, check the connection timeline before blaming the server — a large DNS or TLS segment points to a network or certificate issue rather than slow application code.