- **client** defines how the client should behave
- **verify** defines how to verify that the data stored after a command has
-been run ended up correctly
+been run ended up correct
Each main section has a number of available subsections that can be specified,
that will be checked/used if specified.
may actually consist of multiple words separated by spaces which are treated
together as a single identifier.
-When using curl built with Hyper, the keywords must include HTTP or HTTPS for
-'hyper mode' to kick in and make line ending checks work for tests.
+When using curl built with Hyper, the keywords must include `HTTP` or `HTTPS`
+for 'hyper mode' to kick in and make line ending checks work for tests.
+
+When running a unit test and the keywords include `unittest`, the `<tool>`
+section can be left empty to use the standard unit test tool name `unitN` where
+`N` is the test number.
+
## `<reply>`
### `<data [nocheck="yes"] [sendzero="yes"] [base64="yes"] [hex="yes"] [nonewline="yes"] [crlf="yes"]>`
- `alt-svc`
- `bearssl`
+- `brotli`
- `c-ares`
+- `CharConv`
- `cookies`
- `crypto`
- `debug`
- `GnuTLS`
- `GSS-API`
- `h2c`
+- `headers-api`
- `HSTS`
- `HTTP-auth`
- `http/2`
+- `http/3`
+- `https-proxy`
- `hyper`
- `idn`
- `ipv6`
- `mbedtls`
- `Mime`
- `netrc`
+- `nghttpx`
+- `nghttpx-h3`
- `NSS`
- `NTLM`
+- `NTLM_WB`
- `OpenSSL`
- `parsedate`
- `proxy`
- `TLS-SRP`
- `TrackMemory`
- `typecheck`
+- `threadsafe`
- `Unicode`
- `unittest`
- `unix-sockets`
- `wolfssh`
- `wolfssl`
- `xattr`
+- `zstd`
as well as each protocol that curl supports. A protocol only needs to be
specified if it is different from the server (useful when the server is