Request settings

The Settings tab on the request area holds per-request options (timeout, redirects, cookies) and a section for global network settings that apply to every request in the workspace.

Per-request options

These options live on the request itself, get saved with it, and travel with exports.

Request timeout

How long Rewind waits for the server to start responding before it gives up. Default is 30000 ms (30 seconds). The minimum is 100 ms; the maximum is 300 000 ms (5 minutes).

When a request times out, the response panel shows a red error strip with "Request timed out" and the configured timeoutMs value. The error is also recorded in history with outcome: network_error and error.category: timeout.

Follow redirects

If the response is a 3xx and includes a Location header, Rewind will follow it up to the configured maximum. Uncheck this to leave the redirect in the response panel so you can inspect it. The redirect chain is shown in the response panel's Redirects tab.

Some redirect details worth knowing:

• The redirect method follows the spec: 301 and 302 downgrade POST to GET; 303 always downgrades to GET; 307 and 308 preserve the method and body.
• The Authorization header is dropped on cross-origin redirects.
• Cookies from the cookie jar are re-evaluated at every hop.

Maximum redirects

Cap on how many redirects Rewind will chase before giving up. Default is 10. Set to 0 to allow infinite redirects (not recommended).

Use cookie jar

Turns on the local cookie jar for this request. With it on:

• Cookies already in the jar (matching the request's domain) are sent in a Cookie header.
• Any Set-Cookie headers in the response are stored back into the jar.

The default jar is called default. The Cookies sheet shows the count and lets you clear them. There is no per-request jar in the UI yet; the field is just a toggle.

Global network

The lower half of the Settings tab holds Global network. These settings apply to every request and are stored in the database, not on individual requests.

Proxy URL

A standard HTTP proxy URL, e.g. http://proxy.example.com:8080. Leave blank to make direct connections. The proxy is used for both the request itself and any redirect hops it triggers.

Proxy authorization

A header value to send in the Proxy-Authorization header. Typically Basic … or Bearer …. Treat this as a secret — it is stored in the local database but is otherwise treated like other network credentials.

Verify server TLS certificates

On by default. Uncheck to allow self-signed certificates, MITM proxies, and other invalid TLS configurations. Only uncheck this if you know what you're doing; the option exists for development against local test servers.

Custom CA, client certificate, client key

Three file pickers. Each uploaded PEM file is stored as an attachment in the local workspace and referenced from the network settings. Once uploaded, the label changes from "Custom CA" to "Custom CA added". To replace an uploaded file, upload a new one.

This is the easiest way to point Rewind at an internal API that uses a corporate CA, or to authenticate to a server with mutual TLS.

Saving the network settings also runs a garbage collection pass on attachments: anything that's no longer referenced from network settings is deleted from disk.

Cookies (sidebar)

The Cookies indicator on the Settings tab shows the current count in the default jar. Click Clear cookies to wipe the jar. The same action is also exposed in the cookie listing endpoint for scripts.

What's next?

• Cookies and network — a deeper look at the cookie jar and TLS options
• Troubleshooting — common errors when the timeout fires or the cookie jar interferes
• Data and storage — where the network settings live on disk