A quick flow for deciding where a problem lives.
Section: Status Code Classes
Debug status codes in the right order
text
text
1) Check request method, URL, headers, and body
2) Inspect auth and permissions
3) Follow redirects if needed
4) Check upstream/app logs for 5xx
5) Confirm caching/proxy/CDN behaviorExplanation
This is a practical troubleshooting flow. 4xx responses usually point at client-side request issues or access rules, while 5xx responses usually indicate server-side failure.
Learn the surrounding workflow
Compare similar commands or jump into common fixes when this command is part of a bigger troubleshooting path.
Related commands
Same sheet · prioritizing Status Code Classes
See the full request/response exchange
Use verbose mode to diagnose redirects, TLS, and headers.
HTTP status code classes
Understand the five categories of HTTP responses.
Check headers and status with curl
Inspect the response line and headers only.