Simulating HTTP Response Codes and Network Faults for Testing

In daily testing, it is often necessary to simulate various service responses, such as different HTTP status codes, to verify that the client handles each case correctly.

The article first outlines a complete HTTP request flow, showing the request line, method types (GET, POST, etc.), and how parameters can be passed in the URL or body.

It then presents a simple PHP script (index.php) that reads an optional code query parameter and uses header() to set the HTTP response status accordingly, defaulting to 200.

By sending requests like http://host/index.php?code=404 , the server returns the specified status, which can be observed in the client’s response headers.

The second part describes how to generate network‑level faults using iptables and the tc + netem tools. It shows iptables rules to force a TCP reset on connections containing a “RESET” string, as well as rules to drop packets with a certain probability.

It also demonstrates tc netem commands to introduce packet loss (e.g., tc qdisc add dev eth0 root netem loss 6% ) and explains how to verify the effect with packet captures.

These techniques allow testers to emulate error‑prone environments, such as connection resets, timeouts, and packet loss, improving the robustness of backend services.