Request Settings
Beyond the URL, body, and auth, HTTPBot has a set of request settings that
control how it makes every network call — things like how long to wait before
timing out, whether to follow redirects, and how to handle cookies. These
settings are global: changing one applies to every request you send. You can
reach them from each request's … menu, or from Settings → Request Settings.
For managing cookies, see Cookies.
Opening request settings
Open the request … menu and choose Settings.



Available settings
- Saved responses in history — how many past sends HTTPBot keeps for this request so you can review earlier results. Defaults to 10. See Viewing Responses for where history appears.
- Timeout Interval in Seconds — how long HTTPBot waits for the server before giving up. Defaults to 30 seconds. Increase it for slow endpoints; lower it to fail fast.
- User-Agent — overrides the
User-Agentheader HTTPBot sends. Leave it blank to use the default,HTTPBot/<version>. - Follow Redirects — when on (the default), HTTPBot automatically follows
3xxredirects to the final destination. Turn it off to see the redirect response itself. - Send Cookies — when on (the default), HTTPBot attaches matching stored cookies to the request.
- Store Cookies — when on (the default), HTTPBot saves cookies returned in the response for use by later requests.
- Verify SSL — when on (the default), HTTPBot validates the server's TLS certificate. Turn it off to allow self-signed or otherwise untrusted certificates — useful for local or staging servers. For client certificates and trusted-certificate management, see Certificates.
Settings you change here apply to every request — the same values appear in Settings → Request Settings.
WebSocket request settings
WebSocket connections have their own, separate settings. In Settings → Request
Settings these live under the WebSockets tab (alongside the HTTP tab for
everything above), and you can also reach them from a WebSocket request's … menu.
- Handshake Timeout Interval in Seconds — how long HTTPBot waits for the initial WebSocket handshake to complete before giving up.
- Verify SSL — when on (the default), HTTPBot validates the server's TLS certificate. Turn it off to allow self-signed or otherwise untrusted certificates, which is useful for local or staging servers.
See WebSockets for more on creating and running WebSocket connections.