HTTP (Developer View)
The most common stateless request/response protocol. One "send" is one full round trip.
How to Configure in the UI
- Protocol: HTTP; Method: GET/POST/…
- URL — fill in the path fragment (e.g.
/echo); the host comes from the environment'shttpPre-URL (see concepts). - Fill in params, headers and Body as needed.
- For auth / encryption / assertions, add pre-send / post-response actions (see scripting).
Common body forms: none / form-urlencoded / multipart / JSON / raw. Pick the right type and the tool sets Content-Type for you.
Authentication
Requests can use the built-in auth types:
In practice, "log in once, attach everywhere" is usually done by injecting Bearer via script (see recipes, scenario 1) — less repetitive than configuring auth on each request, and it follows login refreshes automatically.
Cookies / Proxy / TLS / Timeouts
- Cookies: with the environment's cookie policy set to "auto", cookies are injected automatically and Set-Cookie is saved; a single request can override it.
- Transport settings (per request, overriding environment defaults): proxy, whether to verify TLS certificates, connect/receive timeouts, whether to follow redirects and the max hop count, retry counts, etc.
A Complete Example
POST /echo with a JSON body: {"hello":"world"} → the server echoes back {method,url,args,headers,body,contentType,origin}.
The test server also provides these typical scenarios for practice:
| Path | Purpose |
|---|---|
/echo | Echoes the request as-is |
/json | Returns structured JSON (practice extract/assert) |
/oauth2/token + /protected | Login for token → authorized access (recipes, scenario 1) |
/basic-auth, /bearer | Built-in auth verification |
/status/{code} | Returns the given status code |
/redirect/3 | Multi-hop redirects |
/delay | Slow response (practice timeouts) |
/charset/gbk | Non-UTF-8 encoding (practice debugging garbled text, see faq) |
Gotchas
- Send fails with "no base address": most likely the group isn't bound to an environment that has an
httpPre-URL, or the Pre-URL scheme is wrong. - 401/403: confirm the pre-send script really injects the token (temporarily disabling scripts should yield 401 — useful for pinpointing).
- Garbled Chinese in the response: check the charset the server returns, see faq.
Related: environments, variables and the assembly mechanism in concepts.