Routing and traffic control
Route upstream connections, use proxies, and simulate delay, bandwidth, or timeout conditions.
Route to another host
host changes the upstream connection while preserving the original request URL and Host header:
Textapi.example.com host://127.0.0.1:3000api.example.com host://local-api.internal:8443
A direct HTTP or HTTPS target can also replace the upstream destination and path base:
Texthttps://example.com/api/ http://127.0.0.1:3000/local-api/
Upstream proxies
PostGate can forward matching traffic through HTTP, HTTPS, SOCKS4, or SOCKS5 proxies:
Textexample.com http-proxy://127.0.0.1:8080example.com https-proxy://user:password@proxy.example.com:8443example.com socks5://127.0.0.1:1080
Proxy credentials are sensitive. Do not commit them in shared rule files.
Delay and bandwidth
Values are milliseconds for delays and bytes per second for speed limits:
Textapi.example.com reqDelay://200api.example.com resDelay://800uploads.example.com reqSpeed://65536downloads.example.com resSpeed://131072
Use request and response controls independently to model slow uploads, server latency, and constrained downloads.
Timeout and abort behavior
Textapi.example.com timeout://3000api.example.com enable://abort
Timeout values are measured in milliseconds. PostGate also supports selected enable and disable transport flags for capture visibility, abort behavior, forced body writes, and larger merge limits. Other Whistle flags may be preserved without affecting transport; see Compatibility.