Response

Definition

Responses can be used to capture values to perform subsequent requests, or add asserts to HTTP responses. Response on requests are optional, a Hurl file can just consist of a sequence of requests.

A response describes the expected HTTP response, with mandatory version and status, followed by optional headers, captures, asserts and body. Assertions in the expected HTTP response describe values of the received HTTP response. Captures capture values from the received HTTP response and populate a set of named variables that can be used in the following entries.

Example

GET https://example.org
HTTP 200
Last-Modified: Wed, 21 Oct 2015 07:28:00 GMT
[Asserts]
xpath "normalize-space(//head/title)" startsWith "Welcome"
xpath "//li" count == 18

Structure

HTTP 200

content-length: 206
accept-ranges: bytes
user-agent: Test

[Captures]
...

[Asserts]
...

{
  "type": "FOO",
  "value": 356789,
  "ordered": true,
  "index": 10
}

Version and status (mandatory if response present)

HTTP response headers (optional)

Captures and asserts (optional sections, unordered)

HTTP response body (optional)

Capture and Assertion

With the response section, one can optionally capture value from headers, body, or add assert on status code, body or headers.

Body compression

Hurl outputs the raw HTTP body to stdout by default. If response body is compressed (using br, gzip, deflate), the binary stream is output, without any modification. One can use --compressed option to request a compressed response and automatically get the decompressed body.

Captures and asserts work automatically on the decompressed body, so you can request compressed data (using Accept-Encoding header by example) and add assert and captures on the decoded body as if there weren't any compression.

Timings

HTTP response timings are exposed through Hurl structured output (see --json) and HTML report (see --report-html). On each response, libcurl response timings are available:

time_namelookup: the time it took from the start until the name resolving was completed. You can use --resolve to exclude DNS performance from the measure.
time_connect: The time it took from the start until the TCP connect to the remote host (or proxy) was completed.
time_appconnect: The time it took from the start until the SSL/SSH/etc connect/handshake to the remote host was completed. The client is then ready to send its HTTP GET request.
time_starttransfer: The time it took from the start until the first byte was just about to be transferred (just before Hurl reads the first byte from the network). This includes time_pretransfer and also the time the server needed to calculate the result.
time_total: The total time that the full operation lasted.

All timings are in microsecond.

Courtesy of CloudFlare

5.4 KiB Raw Blame History