Simulate slow or timed-out HTTP responses. Test client timeout handling.
The HTTP Timeout Simulator helps you test how your client or application behaves when a request is slow or times out. You configure a delay or use a known slow endpoint; the tool may also offer a mock URL that delays before responding. Developers use it to verify timeout settings, retry logic, and user-facing error messages when the server does not respond in time.
It uses an endpoint that intentionally delays (e.g. sleep) or a proxy that adds delay; your app sees a slow response.
Depending on the tool, you may be able to set connect and read timeouts separately or use endpoints that hang at different stages.
Use only against test or mock endpoints; do not point timeouts at production services that might be affected.
Many clients use 5–30 seconds for HTTP; the simulator often lets you choose delay (e.g. 1s, 10s, 60s).
Combine with a tool that returns 5xx or timeout; run multiple requests and observe retries and backoff.