Network Settings
:::info Screenshot needed — light/dark 📸
settings-window-light.png and settings-window-dark.png — Settings Window, custom title bar
:::
The Network tab (Network & Messaging) controls how requests and responses are sized and stored, how multipart bodies are serialized, whether OS environment variables can be resolved, and how end-to-end tracing headers are added.
To reach it: open Settings, select the Network tab, adjust the controls, changes auto-save on close.
forum Message Settings
| Setting | Default | What it does |
|---|---|---|
| Max Message Size | 10 MB | Maximum size of requests or responses handled by the application. Larger payloads are rejected. |
| Max Historized messages | 300 | Maximum number of messages stored in the history within a workspace. |
When to use — Raise Max Message Size when testing large payloads (uploads, big JSON); raise Max Historized messages to keep more past traffic available in the message history.
How to set — In Message Settings, enter a value in the relevant textbox; the change applies immediately.
code Multipart Object Type
What it does — Sets the Content-Type used for object parts in multipart/form-data requests, determining how each part is serialized. Options: application/json, application/xml, text/xml, application/octet-stream.
When to use — Choose the content type your API expects for the object parts of multipart uploads.
How to set — Open the Default multipart object type dropdown and pick a value; the change applies immediately.
terminal Environment Variables
What it does — Allow OS environment variables: when enabled, ${VARIABLE} tokens in request fields fall back to OS environment variables if not defined in the test environment. Default: on.
When to use — Keep enabled to pull secrets/config from the machine environment. Disable in locked-down enterprise deployments where environment access must be blocked.
How to set — In Environment Variables, toggle Allow OS environment variables; the change applies immediately.
link HTTP Trace Context
End-to-end tracing propagates correlation IDs across the HTTP client and simulated HTTP servers.
W3C Trace Context
What it does — Enables support for W3C Trace Context on all supported services (HTTP Client, HTTP Server) — the industry standard for distributed tracing. Default: off.
When to use — Enable to correlate Aethrix Studio traffic with backend traces in an OpenTelemetry/distributed-tracing setup.
Custom Trace Header
What it does — Enables a custom end-to-end tracing HTTP header for environments that don't use W3C Trace Context. Default: off.
When to use — Enable when your systems correlate requests through a proprietary header instead of traceparent.
| Setting | What it does |
|---|---|
| Trace Header Name | The end-to-end tracing HTTP header name (for example, X-Correlation-Id). |
| Trace Header Value | The value template for the end-to-end tracing HTTP header. |
How to set — In HTTP Trace Context, toggle Custom Trace Header, then fill in Trace Header Name and Trace Header Value; the change applies immediately.
W3C Trace Context and Custom Trace Header can be enabled simultaneously.