Performance ModifyFlip HTTP Code• 4 min read

How to Simulate HTTP Error Codes (500, 401, 404, 503)

Summary: Flip successful 200 OK responses to 401 Unauthorized, 404 Not Found, 500 Internal Server Error, or 503 Service Unavailable to verify error handling.

Why This Rule Matters for Developers & QA

Reliable software requires testing unexpected backend outages. Manually simulating server crashes or auth expiries in production is dangerous; doing it at the client layer is safe and immediate.

Step-by-Step Implementation Guide

1

Match Target Endpoint

Specify the endpoint to fail (e.g. `*/api/v1/payment/checkout`).

2

Choose Target Status Code

Select the desired status code, such as `500 Internal Server Error` or `401 Unauthorized`.

3

Verify UI Error Boundary

Ensure your app displays appropriate user feedback, retry buttons, or re-authentication modals.

Configuration Snippet

How to Simulate HTTP Error Codes (500, 401, 404, 503) — proxyceptor-rule.json
JSON
{
  "id": "rule_test_server_500",
  "pattern": "*/api/v1/payment/checkout*",
  "action": "flip-status",
  "statusCode": 500,
  "statusText": "Internal Server Error",
  "enabled": true
}

Frequently Asked Questions

Explore More Debugging Guides

Redirect / Rewrite
URL Modify & Redirect
4 min read
JSON Deep Merge
Payload Modify & Deep Merge
5 min read
Inject Headers
Request Header Modify
4 min read