Back to Playground
Network Issues
HTTP errors, slow responses, failed requests, and edge cases in fetch/XHR calls.
HTTP 400 Bad Request
Network
Server rejects the request due to invalid input.
Network event: status 400, error body in responseBody
HTTP 401 Unauthorized
Network
Request missing or invalid authentication credentials.
Network event: status 401
HTTP 403 Forbidden
Network
Authenticated but not authorized to access the resource.
Network event: status 403
HTTP 404 Not Found
Network
The requested resource does not exist on the server.
Network event: status 404
HTTP 500 Internal Server Error
Network
An unhandled exception occurred on the server.
Network event: status 500, error message in responseBody
HTTP 503 Service Unavailable
Network
Server is temporarily overloaded or in maintenance mode.
Network event: status 503
Slow Response (3 seconds)
Network
A delayed server response — tests that timing is captured accurately.
Network event: timing ~3000ms, status 200
Large Response (>5000 chars)
Network
Response body exceeds the 5000 character capture limit — tests truncation.
Network event: responseBody truncated with "...[truncated]"
Malformed JSON Response
Network
Server returns Content-Type: application/json with invalid JSON body.
Network event: responseBody is raw invalid JSON string
POST with JSON Body
Network
Sends a POST request with a JSON payload — tests requestBody capture.
Network event: method POST, requestBody contains JSON
XHR GET Request
Network
Uses XMLHttpRequest instead of fetch — tests the XHR interception path.
Network event captured via XHR intercept
Network Failure (Connection Refused)
Network
Fetches from a port with nothing listening — triggers a network error.
Network event: status 0, error field populated
Redirect Chain (3 hops)
Network
Server responds with 302 redirects through 3 hops before returning 200.
Network event for final 200 response after redirects
Custom Request & Response Headers
Network
Sends custom request headers and receives custom response headers.
Network event: requestHeaders and responseHeaders contain custom values