Learn / Answers

What do HTTP 4xx and 5xx errors mean in a capture?

HTTP status codes from 400 to 499 mean the server rejected the request (not found, unauthorized, bad request); 500 to 599 mean the server failed while handling it. Either way the network delivered the request and the response, so the problem is in the app or server, not the network.

What it looks like in the packets

  • A complete TCP connection and HTTP request.
  • A response with a status of 400 or higher.
  • Over HTTPS, the status is encrypted and invisible in the capture.

Common causes

  • 5xx: an app crash, overload, or a failing backend (502/503/504 from a proxy or load balancer).
  • 4xx: a wrong URL (404), missing credentials (401/403), or a malformed request (400).

What to check

  1. Match the request time with server logs.
  2. For 502/503/504, check the backend behind the proxy.
  3. For 4xx, compare the requested path and headers with what the API expects.

Wireshark display filters

  • http.response.code >= 400HTTP errors
  • http.response.code >= 500server errors only

How Blame Finder flags it

Warning for 5xx; Low for 4xx. Upload a capture and the finding links straight to the packets behind it, with the most likely culprit at the top.